Hi,
the alias is here on purpose. Alias of identityProvider is guaranteed to
be unique across the realm. This is not the case for providerId. For
example you can have 3 SAML identity providers configured in your realm.
Then all those 3 providers will have same providerId, so you won't know
which one you want to work with.
On the other hand, when you have alias, you can always lookup the
providerId from it.
Marek
On 09/11/18 19:11, Chris Brandhorst wrote:
Hi all,
Redirect by Bruno from
https://issues.jboss.org/browse/KEYCLOAK-8773:
We came across the following. In SerializedBrokeredIdentityContext#serialize, the
identityProviderId property is filled with the alias of the IdentityProviderModel, instead
of (what we would expect) its providerId.
Relevant line:
https://github.com/keycloak/keycloak/blob/b478472b3578b8980d7b5f1642e91e7...
We feel this behaviour is semantically incorrect: we were checking against this property
in one of our authenticators, but our code did not work for another identity provider of
the same type. After some digging we thus found that we were expecting the providerId
(coded value) but were actually reading the alias (configured value).
Simply throwing this in as a possible improvement. What do you think?
Regards,
Chris Brandhorst
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev