- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi there!
I believe this particular use case is not supported. I've looked at the Cognito documentation and there is no mention of this use case.
My guess is that it has to do with Okta working with a per organization model in which there is no general Okta directory of accounts (i.e. in the case of Google, I can personally go and create an account unrelated to any particular organization) that is managed by Okta, except those managed by individual organizations.
I hope this helps (if so, please mark this as an answer).
Yes looks like that however is there any problem to have any number of OIDC providers created by backend runtime ? The solution I mentioned in my post.
You can have multiple Okta instances registered as IdP within the Cognito User Pool. It is the same process as having just one (just rinse and repeat).
This tutorial is for SAML Okta/Cognito integration, but you end up with an "Okta Application" that can be reviewed and published inside Okta. I believe any organization should then be able to use it, but I'm not 100% sure.
Contenus pertinents
- demandé il y a 5 mois
- demandé il y a 8 mois
- demandé il y a 2 mois
AWS OFFICIELA mis à jour il y a un an- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
One solution is to dynamically create OIDC integration in cognito user pool from the backend by asking client id & domain from the user. However I am wondering if there is something in built cognito provides which I am missing or any standard solution to solve this problem.