Is this expected behavior that when placing two different self-service SSO tickets into the same browser tab to create a connection, the identity provider from the first ticket is automatically selected for the second one ? This behavior is affecting our flow, as both tickets are been open in the same modal.
Steps:
Create Self Service SSO
Copy and paced URL into a new browser tab and hit Enter
Hit ‘Get Started’ and select identity provider, DO NOT hit Next
Create another Self Serve SSO ticket
Copy and paced URL into the same tab that you user for previous ticket and hit enter
Observe that provider from previous ticket is automatically selected
I have just tested your reproduction steps and could not get the same results.
When I created the self service SSO tickets, the tickets adhere to the connection I specified in my request accordingly.
For the first ticket, I used SAML. And for the second ticket, I used OIDC. After following your steps, both the first and second tickets opened with the respective identity provider I specified when creating the self service SSO ticket.
Have you made sure that you specified a different connection for each of the self service SSO tickets?
I retried my tests to create a connection rather than edit one and ensured I pasted the second URL in the same tab as the first URL.
As a result, I managed to reproduce the issue you shared. After selecting my identity provider in the first URL and not clicking Next, once I pasted the second URL in the same tab as the first, it seems to automatically click Next with the selection I made in the first URL.
However, when I take that same self service SSO ticket and paste it in a new tab, it seems to load correctly.
I have reported this behavior to our Engineering team to investigate further.
For now, my best recommendation is to open the self service SSO ticket in a new tab if you have multiple SSO setup links.