Timeline for SAML authentication flow, do not require user to click "Log in with <sso idp option>"
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2019 at 17:03 | comment | added | identigral | If domain-Force is an SP that is linked to the IdP and the session exists at IdP from steps 2-3, you shouldn't be prompted for login in step 6. Perhaps the link in step 4-5 is "wrong" (it doesn't engage the IdP/SP on SF side) or the IdP/SP integration on SF side is not implemented correctly. | |
| Jun 11, 2019 at 16:19 | comment | added | LeeZilla | Only in the source SP initiating the request. Otherwise it is doing the same workflow, authorizing a user to the second SP. | |
| Jun 10, 2019 at 17:06 | comment | added | identigral | Is the IdP in step 2 different from IdP in step 6? | |
| Jun 7, 2019 at 3:20 | comment | added | LeeZilla | Programmatically. There are multiple login pages created for this community for all of the other inbound routes users might take, so the primary /Login can be dedicated to this one task. Said simply: If the user is on /Login their ONLY next step is sending the IdP the auth request. | |
| Jun 6, 2019 at 2:24 | comment | added | identigral | If you remove step 5, how does the system know where to redirect the user? Perhaps you can write out the steps in to-be state, it would help clarify. | |
| Jun 5, 2019 at 16:25 | review | First posts | |||
| Jun 5, 2019 at 21:03 | |||||
| Jun 5, 2019 at 16:23 | history | asked | LeeZilla | CC BY-SA 4.0 |