Is Public An icon of a human eye and eyelashes. Telephone An icon of a traditional telephone receiver. Profile An icon that resembles human head and shoulders. Linked In An icon of the Linked In "in" mark. Facebook An icon of the Facebook "f" mark. Caret An icon of a block arrow pointing to the right. Cancel An icon of a circle with a diagonal line across. (At least, I hope I'm understanding your situation correctly.Calendar An icon of a desk calendar. The whole point of a dedicated Identity Provider with oauth2/oidc support is to make sure that clients do not have to deal with things like external providers. In fact, if you clone and ng serve my sample application it connects to that very identity server 4 instance and supports external providers, without the client code having anything related to those providers. ![]() ![]() You can also easily "see"/"prove" this by pointing folks at the demo identityserver that also supports external logins. There is no way to do anything at all on the Angular side of things, at least not when using this library. If you use this library to do either one of the last two, the library will indeed send your users to /connect/authorize as per the oauth2/oidc specs, but then the back-end has to deal with forwarding users to external providers and afterwards rerouting them back. password flow (irrelevant for your case since you want external logins providers via IDS4).As far as I know, the question from your back end team makes no sense, for sure not with this library and OIDC flows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |