SAML logout causes errors

[yadvr]

problem

Tried this on https://qa.cloudstack.cloud/simulator where after logging as rick user, when trying to log out caused this error:

I'm not sure if it's an env issue or CloudStack issue on handling/redirecting to login page after successful logout.

versions

ACS 4.21 with simulator and public SAML service

The steps to reproduce the bug

No response

What to do about it?

Likely we need to check if logout is clearing out the cookies etc and redirecting properly. It could be also qa server specific config (around saml settings - on a quick look I couldn't find any issue).

[yadvr]

On a little investigation, I think the cookies are not getting cleared (which could be an env issue, as on qa server /client/ is redirected from /simulator/ ...)

But this needs investigation if the cookies are not getting cleared (on the same domain).

[weizhouapache]

could this be same as #11078 which has been fixed by #11361 ?

[yadvr]

Can test with RC1

[yadvr]

@harikrishna-patnala fyi, this could be tested using the QA env (qa.cloudstack.cloud)

[RosiKyu]

@harikrishna-patnala I was not able to reproduce this on 4.22

And before the Logout:

[harikrishna-patnala]

Thank you @rosi-shapeblue for checking.

@rohityadavcloud please check with 4.22 RC build in your environment, if it repeats, please reopen this ticket and we will see what can be fixed based on the situation. Thanks.

[poddm]

@harikrishna-patnala, I'm seeing this issue in 4.22 initially reported here #11078

I'm not seeing this fix pulled into main, 4.22.2 releases, nor in the 4.20.2 release.

• fix: Make logout function more robust to prevent session issues #11361

I might be overlooking this -

• (main) https://github.com/apache/cloudstack/blob/main/ui/src/store/modules/user.js
• (4.20.2.0) https://github.com/apache/cloudstack/blob/4.20.2.0/ui/src/store/modules/user.js
• (4.22) https://github.com/apache/cloudstack/blob/4.22.0.0/ui/src/store/modules/user.js

Additionally, these screenshots look to be LDAP or local user logins. Your SSO login field looks disabled.

@harikrishna-patnala I was not able to reproduce this on 4.22