anarsultanov / keycloak-multi-tenancy

Keycloak extension for creating multi-tenant IAM for B2B SaaS applications.
Apache License 2.0
103 stars 11 forks source link

Unique password policy for each tenant #10

Closed cocadepoma closed 5 months ago

cocadepoma commented 7 months ago

Hello, I am planning to implement Keycloak in a project and I would like to have different password policies defined for each tenant, does this extension allow me to do it?

Thank you so much for your attention.

anarsultanov commented 7 months ago

Hello @soyl3y3nd4,

Unfortunately, the extension does not currently support different password policies for each tenant. However, you can still implement tenant-specific Identity Providers (IDPs) and allow tenants to manage their own policies through their respective IDPs.

If you have any further questions or need assistance, feel free to ask.

cocadepoma commented 7 months ago

Hi @anarsultanov, thank you very much for your answer.

Where can I find an example of how to build what you said?

tenant-specific Identity Providers (IDPs) and allow tenants to manage their own policies through their respective IDPs

I plan to have a Realm with several clients (frontends and backends) and then every customer with their own Realm, users, password policies, etc... is this possible to do in Keycloak?

If this is possible, for example, if a user is not authenticated and tries to enter into a protected client, where it should be redirected, which Realm?

Sorry for my confusion, and thanks for your help.

anarsultanov commented 6 months ago

Hi @soyl3y3nd4, no problem at all!

It looks like your use case is completely different from the intended purpose of this extension.

As for your question, I'm not sure if your idea is possible, as users and clients are realm-specific in Keycloak.

For more guidance, I recommend checking the Keycloak documentation or reaching out to the Keycloak community.

Feel free to ask if you have any more questions!

github-actions[bot] commented 5 months ago

This issue is stale because it has been open for 30 days with no activity. If this issue still applies please comment otherwise it will be closed in 7 days.

github-actions[bot] commented 5 months ago

This issue was closed because it has been inactive for 7 days since being marked as stale.