[keycloak-user] avoiding save external-Provider-Users localy

[Marek Posolda]

It's not available OOTB. I think that JIRA for this already exists.

You may possibly tweak by yourself and override first-broker-login to 
flow to not register user to the database, but instead put him just 
in-memory. I think there are ways to do it. Maybe see some 
quickstarts/examples for authentication providers and UserStorageProviders.

Depends also if you are in cluster as then in-memory users may not be 
sufficient (EG. Currently UserSession requires existing UserModel. So if 
UserModel is just in memory on cluster-node1 and can't be found on the 
other cluster-node2, it may be an issue)

Marek

On 06/02/18 12:06, abdelkader samir wrote:
> Hi all,
>
>
> We are currently using a Keycloak (3.3.0.Final), there you are binding a external sso Provider as "Identity Providers"
>
> Until now everything is working fine.
>
>
> Now we figure out that Keycloak are saving the user in its local database (
>
> see http://www.keycloak.org/docs/3.0/server_admin/topics/identity-broker/first-login-flow.html )<http://www.keycloak.org/docs/3.0/server_admin/topics/identity-broker/first-login-flow.html>
>
>
> According to Keyclaok documentation: Keycloak needs the local users, but we don't know why?
>
>
> It is possibile to avoid saving the user in Keycloak?
>
>
> Thanks and regards
>
> Adam
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user