This is the SAML process flow:
Auth0 = Identity Provider (could be any identity management platform)
Meraki Dashboar = Service Provider
1.The user tries to log in to Meraki Dashboard from a browser.
2. Dahboard responds by generating a SAML request.
3. The browser redirects the user to an SSO URL, Auth0
4. Auth0 parses the SAML request and authenticates the user. This could be with username and password or even social login. If the user is already authenticated on Auth0, this step will be skipped. Once the user is authenticated, Auth0 generates a SAML response.
5.Auth0 returns the encoded SAML response to the browser.
6.The browser sends the SAML response to Dahboard for verification.
7.If the verification is successful, the user will be logged in to Dahboard and granted access to the resources that they are authorized to view/modify.
Since information by meraki does not metion about type of SAML in sequence, I checked general doc in "https://developer.okta.com/docs/concepts/saml/#planning-for-saml".
It says [A SAML Request, also known as an authentication request, is generated by the Service Provider to "request" an authentication."]
A based on the following documents under SP-initiate SAML
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
sattori
1 week, 1 day agorobby77
1 week, 4 days agornunes1110
1 year agokobaba
1 year, 6 months agoLordHammer
1 year, 10 months ago