Error - Oops something went wrong on ISE 2.3

[umahar]

We have an ISE cluster running ISE 2.3 with 2 PSNs.

Guest and Sponsor portals are working fine on one PSN while the other PSN is giving an error.

"Oops something went wrong. Access denied. Contact your administrator"

I've seen a couple of bugs related to this in previous versions.

Has anyone encountered anything new regarding this issue on 2.3 ?

[Nidhi]

Can you explain the steps when you get this error ? Also, do you have a TAC case opened for this ?

[umahar]

This error is seen on the endpoints when they get redirected to the second portal.

I have a TAC case opened.

[umahar]

Hi experts,

So I have more visibility on the issue.

The customer has 2 PSNs but has mapped sponsor portal to FQDN of PSN1. He is shutting down PSN1 and expects the sponsor portal to work on PSN2 using the FQDN of PSN2 with the reasoning that he is able to reach the correct IP of PSN2. I am quite sure that this will not work as PSN is throwing error ' Oops something went wrong' to the user. In all my other deployments I have used F5 or DNS load balancing.  I have also verified this behavior by switching the FQDNs between PSN1 and PSN2.

Could anyone confirm that ' PSNs will only respond to sponsor portal requests on the FQDNs to which its mapped ' ?

[Nidhi]

Yes you are right. The FQDN of sponsor portal should resolve to IP address of one of the PSNs. 

You can use loadbalancer to achieve what you are looking for. in that case, the sponsor portal FQDN will point to the load balancer VIP. 

Thanks,

Nidhi