You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My UseCase for organizations: 4 WebApps -- keycloak -- IdP(saml) I want the 4 webApps authorized by keycloak (CIAM) and authenticated by external IdP.
A user in an Org need to have entitlement to one or many of the WebApps, I can use a custom attribute entitlement=webApp1 for that, each WebApp have there own Team to managed it's users and Orgs, this could be done using the Admin Console but each admin will have access to each Users and Orgs which is not desirable, I guess separate Realms per WebApp could work but then no SSO, if a User is entitled to more than one WebApp. An idea is to create another Hierarchy in KC, i.e community and you can create many community and Orgs and Users are linked under each community in the same Realm. (an admin console per community)
The second issue I have is that the WebApp Teams create Orgs and Users and I want to link the pre-created users with the authn User of the external IdP, I guess Mapper but the issue is that the only attribute back from the IdP is a Federated-Token, so I need a first-time login flow (invite) that maps the Federated-Token to the User in keycloak. One idea is the have keycloak to send an email to the user when a WebApp Team add a User to an Org with a link that sends the User to the IdP and after successful authn get a page and enter a Temporary OneTimePassword which was sent in the email and the flow Map the Federated-Token to the keycloak User and adding the Federated-Token as an attribute, next time the user login keycloak will check the attribute (federated-Token) mapping and if match login if not then bring up the registration page.
The question is can I do the Flow in my UseCase in keycloak or is there a better way to solve the issue with only get back a federate-Token from the IdP which is not known at the time the WebApp Team is creating the user?
I would like to delegate the authority to an admin role of each Org, I read that Administrative Organization is on the todo list. I guess I could use groups for users like OrgAdm and OrgMember and then use the API's.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
My UseCase for organizations: 4 WebApps -- keycloak -- IdP(saml) I want the 4 webApps authorized by keycloak (CIAM) and authenticated by external IdP.
A user in an Org need to have entitlement to one or many of the WebApps, I can use a custom attribute entitlement=webApp1 for that, each WebApp have there own Team to managed it's users and Orgs, this could be done using the Admin Console but each admin will have access to each Users and Orgs which is not desirable, I guess separate Realms per WebApp could work but then no SSO, if a User is entitled to more than one WebApp. An idea is to create another Hierarchy in KC, i.e community and you can create many community and Orgs and Users are linked under each community in the same Realm. (an admin console per community)
The second issue I have is that the WebApp Teams create Orgs and Users and I want to link the pre-created users with the authn User of the external IdP, I guess Mapper but the issue is that the only attribute back from the IdP is a Federated-Token, so I need a first-time login flow (invite) that maps the Federated-Token to the User in keycloak. One idea is the have keycloak to send an email to the user when a WebApp Team add a User to an Org with a link that sends the User to the IdP and after successful authn get a page and enter a Temporary OneTimePassword which was sent in the email and the flow Map the Federated-Token to the keycloak User and adding the Federated-Token as an attribute, next time the user login keycloak will check the attribute (federated-Token) mapping and if match login if not then bring up the registration page.
The question is can I do the Flow in my UseCase in keycloak or is there a better way to solve the issue with only get back a federate-Token from the IdP which is not known at the time the WebApp Team is creating the user?
All reactions