3 ms·
I have implemented OAuth both as a client and a server. The most complicated part is the scattered documentation, and little gotchas from different providers. I
by frizlab 8mo ago
I have implemented OAuth both as a client and a server. The most complicated part is the scattered documentation, and little gotchas from different providers. In itself, the whole thing is not complex.
- user3939382 8mo ago> The whole thing is not complex Meanwhile https://www.couchbase.com/blog/wp-content/uploads/2021/05/oauth2-auth-code.png https://www.couchbase.com/blog/wp-content/uploads/2021/05/oa...
- everybodyknows 8mo agoThe diagram shows five boxes, apparently each representing a server, but I am not at all clear on which (of exactly two?) legal business entities controls certain of those servers.
- magicalhippo 8mo agoThat's just a very confusing diagram of the process, which has multiple separate boxes for the same entities. The diagram on Microsoft's page[1] for that exact same scenario/flow is much clearer IMHO. [1]: https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-auth-code-flow https://learn.microsoft.com/en-us/entra/identity-platform/v2...
- kennywinker 8mo agoI hope this was meant as a joke…
- magicalhippo 8mo agoWhy would it? The first diagram is literally all over, with just small labels to remind you that this box over here relates to that box over there. The Microsoft diagram clearly show the parties involved, who they communicate with and in which sequence. As I mentioned in another post, I found the MS pages very helpful to understand OAuth 2.0, and the clear diagrams was a large part of that.