This was fantastic! There are too many people out there attempting to post technical instructional videos who don't really have an in depth understanding of the material, or don't know how to explain it. This was a rare find. Thanks for posting!

It's the best video that explains the whole story of SAML. The extraordinary part is explaining "Most common weak points" start from 17:32!

Best thing I found on UKposts for SAML security audit. Thank you very much for detailed information about SAML including the flows.

Okta's technical guides around identity never disappoint!

This is the best lecture I have seen including school to online tutorials, I love you!!!

THE BEST video for developers to keep things secure!

understood SAML from developers' view at last.... very easily... thank you 🦃

Very well organized guide and superbly presented. You are excellent teacher. Thank you.

Amazing, thank you for all the work you do!

I know this video is old but it's still chock full of information. Thank you for the video sir.

Best ever video on SSO... Simply love it

Awesome effort . Very good. Thank you for spending the time to make this presentation

Thank you so much for this. Amazing explanation !

Best video on SAML ever! Kind had to grin at 7:02 where he talks about the convenience feature of saml metadata! Real shame that okta lacks the upload SP metadata feature ;-) this is quite standard for other IDPs

Concepts clearly told and upto Point, Could You do couple of more Videos on QnA involving guys to spend some time along revolving around common Usecases specific to Vendors.

Great, beneficial introduction to SAML, thanks!

Wow, such a great video. I just wanted to know about SAML and IdP workflow but this was so well explained and entertaining that I had to watch it until the end.

Nice once. The concept is clear now. Can you do a video on SAML + NodeJs

very nice, thanks for taking the time!

Best explanation... Thank you.

Nice work, Nick!

Great explanations regarding SAML like it.

Amazing video, very clearly explained

Good video. Could you show viewing and debugging SAML requests/responses in Chrome or FF. Also can you show some examples of claims rules.

Really great explanation! Thank you so much!

Awesome explanation!

Awesome explanation, thanks a lot! Now I understand better this flow!

Good one. Thank you.

hello thanks for the explanation it was very helpful i want to know how to configure a saml with a loadbalancer i had problem that the load balancer doesn't sign on the SPs

Excellent Sir !

OktaDev videos are the best ever in explaining the concepts! ❤ Would have been much better if you have explained SAML bindings

This has been very helpful!!!

Excellent video.

Very well explained. Thanks

Amazing explanation 🙇‍♂️

Simply Superb

Really useful video! Thanks a lot

Perfect explanation, thanks!

thats what I am looking for..perfect explanation

very well explained

Fantastic video!

Totally worth it.

Excellent Video. TBH! i was confused earlier on how to read a SAML response.

Terrific!

Just great awesome explanation

Very clear

@OktaDev, In 'Limit the XML Parser" , is the sub heading 'Disable Document Type Definition (DTD) Fetching' wrong and ought to be 'Document Type Definition (DTD) Fetching? ( Felt like that from context )

Fantastic!

Http artifect binding in SAML , can u explain real use case and which kind of attack gets eliminated and how to use it

@oktadev is there a difference between calculation digest value for saml version 1.0 and 2.0?

Very clear, thanks a lot for that!

How would this change when using a CLP (Central Login Page) external to all of this

Correct me if I'm wrong, but as I understand it SSO only happens when a user performs an Identity Provider Initiation. By providing your credentials to the Identity Provider once, the Identity Provider can send SAML responses toward any application or service you're trying to use. However, if as a user you're required to start the SAML process with the Service Provider first (Service Provider Initiation), then a SAML Request is sent to the Identity Provider who in turn returns a SAML Response. This interaction is only valid for that one, specific Service Provider, not all Service Providers, meaning that you'd have to repeat this login process again for any other application you might want to use. In other words, for any Service Provider that requires you to begin the authentication process with itself first, you're going to be redirected somewhere to provide your login credentials. If you have 3 Service Providers asking to begin the process with each of them, then you're not really participating in a Single-Sign-On experience -- Is this correct?

thank you so much, grand respect.

very very very good one

Great video thank you, well done. However i do have to disagree with you on one thing, using a SSO may be more convenient but it is less secure. The best security IMO is to keep PW under personal care and just find a way to remember them. This is less convenient but the fewer parts involved in security validation the better. It is similar to telling noone your password vrs telling 5 friends with the promise they wont tell anyone. Security is only as good as the weakest link and the more links involved the less secure IMO. I code for SSO but i do not use SSO personally. Each of us must make the choice based on convenience.

20:58 This could also be mitigated by making sure all the assertions in the SAML response are signed, right?

This is the best video explaining SAML

How to generate SAML request xml? Should the developer of the application generate and supply value on the xml tags?

Thanks

Thanks you so much, for explain SAML

Clean and perfect 🔥

Hi sir, but how system is passing the username / email id in request to validate at IDP

i like the security part of the vedio

great guide - thanks for video

I love u man. Thanks to you, I'll probably get a better job. I'll keep you updated

Sir can u clarify that all the SP - IP communication is via client browser and not directly between the two parties. Or is there a back channel between the two parties in addition to the client as the intermediary.

Good explanation.

now i understand! great explanation. do you have a video using simpleSamlPhp? thanks in advance

simply Wow!!!

27 minutes on youtube sometimes is way better than 4 hours in a lesson room.

Excellent explanation, thanks. I finnaly understand SAML and difference beetwen this protocol and OAuth/OpenId Connect. I alse recommend watch video about OAuth/OpenId Connect by Nate Barbettini in this chanell

very well explained.

Perfect - thanks

why do we need to have user profile at Service provider? I am under the assumption that all user details are only in IDP, and not in SP. why do we need to have user details in SP? In that case, can't we skip SSO and login directly into SP if SP is also having user details. Doesn't having user details in IDP and SP keep information at two places? Can anyone help explain it, please.

Really good

Identity Provider means that all users has to be registered there with actual credentials?

Thanks mate!

Great video

Thank you so much

Thank you.

Great video! :)

Can you explain a bit on how to Validate a signature

Thanks for ur time

attrubtes?

Good stuff

this was good , however i need some more info on Canvas vs SAML

Why is he only talking into my right ear?

Well, it's better to walk through a SAML workflow and then explain the SAML terms and concepts. It will be more clear.

This is a good answer to why is still easy to hack a big company :)) . The pour dev has to be extra carefull when configuring the xml parser :)))

ATTRUBTES!!

Confusing.

It is funny that you speak of OIDC as a replacement for SAML. Meanwhile Okta still does not support OIDC for SCIM provisioned application, forcing me to learn about this SAML in the first place...

Really useful intro but bro, I think your sweater was on inside out

Oauth forever, fk saml

Attrubtes

What a joke of a system. No one should be using SAML and we just need to migrate away from this shit.

SAML looks like it was made me some old white guys.