
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2017 04:27 PM
Hi
I wanted to provide some feedback after a TAC case of mine revealed a deeper understanding of how the ISE Sponsor Portal health check works. I am referring to the brilliant BRKSEC-3699 which gives us examples of how to do it.
When I initially used this in my ISE 2.2 deployment I followed the ISE 1.3 Example verbatim in my F5 LTM and all was working well. And then one day I modified my Sponsor Portal and then it broke the health check. Here is why ... it's obvious now, in retrospect, but I didn't realise that the GET string example above was referring to the Portal Name. The BRKSEC example works well as long as you don't customise the Portal Name.
Solved! Go to Solution.
- Labels:
-
Identity Services Engine (ISE)
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2017 05:43 PM
Hi Jason - agreed - too much coffee ... too much multi-tasking
With any luck ( chyps ), my amendments could make it into the next BRKSEC-3699 updated PPT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2017 04:52 AM
Great feedback! Thank you for clarifying this and writing it out so that it is easy to understand.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2017 07:48 AM
great stuff you should post this as a document or blog instead of a question
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2017 05:43 PM
Hi Jason - agreed - too much coffee ... too much multi-tasking
With any luck ( chyps ), my amendments could make it into the next BRKSEC-3699 updated PPT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2020 10:15 AM
