Comment on 400 Bad Request Error on the Cisco ISE 2.3 Guest Portal by Eric January 4, 2019I had the same issue and this workaround fixed it.. but I think I found the root cause (at least for us)
In the Auth Policy we have it redirect to the domain ise.companydomain.com. that domain resolves with two A records for the two node cluster. when clients would get redirected to the second node, this error would appear, but would work on the first node just fine. I’m guessing the logos on the second node are the problem in some manner and removing them fixes the issue. but if I redirect them to just the main node either by going directly to its hostname or removing the second DNS A record entry it works fine. Only problem with that is you loose redundancy.. so for now.. removing the logos is our fix. Thanks for the article!Comment on Not My Problem – Or Should It Be? by gianpaoloboarina December 15, 2018There is a very thin line between “Not my Problem” and getting sucked in external requests and losing sight of the important targets.
Unless you’re a sociopath “yes” is easier than to say “no”.
There can’t be a general rule because every request is different but there has to be a filter to protect our time without being rude or create relationship problems.
We must accept that some people will be dissatisfied by our “no” and may complain about that. Maybe gift them a copy of https://www.the1thing.com/ so they understand