You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have one enterprise application in azure portal with SAML signle-sign-on and have 2 projects in Oneuptime tool
Now I have configured the SSO for both 2 projects with same enterprise application ,
And logged into one project using SSO authentication in oneuptime .
After logged in I am trying to switch into another project which has same SSO configuration with same enterprise application but the browser page is continuously loading it is not allowing me to switch into another project is this expected behavior? or do I need to logout and login again using SSO to my another project?
To Reproduce
Steps to reproduce the behavior:
Create one SAML enterprise application in Azure portal
Create 2 projects in oneuptime
Now configure SSO for both projects with same above created enterprise application
Invite the user in enterprise application
Now try to login into one project in oneuptime using SSO authentication
Once you login try to switch into another project
It won't allow you to switch into another project the browser page will continuously load
Expected behavior
Either the oneuptime tool should allow me to switch into another project or it should ask SSO authentication again while switching into another project because I am using same SSO enterprise application for both projects
-Oneuptime Version - 7.0.3357
Deployment Type
self hosted (7.0.3357)
The text was updated successfully, but these errors were encountered:
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Either the oneuptime tool should allow me to switch into another project or it should ask SSO authentication again while switching into another project because I am using same SSO enterprise application for both projects
-Oneuptime Version - 7.0.3357
Deployment Type
self hosted (7.0.3357)
The text was updated successfully, but these errors were encountered: