OpenSearch: v2.6.0
OpenSearch Dashboards: v2.6.0
Chrome: 115.0.5790.171
I have an issue with logging in via SSO when a URL containing an index and query are pasted in to the OpenSearch Dashboards application. The issue is very similar to that noted in OSD dashboard url redirection fails for the first time in Safari browser and load the dashboard lists page instead of specific dashboard - #3 by yogiks
The problem is that when you logout, having logged in via SSO and paste a link to a discover search containing an index and a term you end up on the discover home page, rather than at the original URL.
To demonstrace, login via SAML/ADFS SSO. View some logs under the ‘Discover’ tab. Take a copy of the URL
https://REDACTED/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-2d,to:now))&_a=(columns:!(_source),filters:!(),index:‘:sample-index-’,interval:auto,query:(language:kuery,query:‘lag_ms%20%3E%3D%2037000’),sort:!())
Logout and paste link above in:
https://REDACTED/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-2d,to:now))&_a=(columns:!(_source),filters:!(),index:‘:sample-index-’,interval:auto,query:(language:kuery,query:‘lag_ms%20%3E%3D%2037000’),sort:!())
Click on SSO login link and end up on
So, I do not end up on the app/page I was expecting. This behaviour does not happen when I logout and paste the link and login via AD credentials. When using that method I end up in the Discover app with the index and search query set correctly.
Has anyone encountered this before? I find it quite confusing to follow all the redirects involved in the SAML handshake but feel that a redirect is somehow getting lost or reset in the flow.
I’ve been looking at the requests during the SAML/SSO call once logged out and can see
/auth/saml/login?nextUrl=%2F&redirectHash=false and I can then see the call to the ACS responding with the web root location, ie / and then a redirect to /app/home but I’m not really sure what this is telling me.
I have tried to use the short url as a workaround (suggested in the post above) but that does not seem to work in this case.
Anyone able to help or able to reproduce this issue themselves?