Re: [keycloak-dev] [KEYCLOAK-996] - Allow application to select provider

----- Original Message ----- I understand your point. You are basically talking about "acr" and "amr" fields of id_token. After reading a little bit more about the meaning of both fields, I realized that acr provides more meaning than amr. The reason is that you would prefer a "context" than rely on specific authentication mechanisms in order to do access decisions. For instance, SAML provides something similar to amr and for some people that is one of the SAML specs mistakes. And there are discussions on OIDC mailing lists about the real value of "amr". IMO, makes much more sense to rely on the context used to authenticate the user than on an individual (or multiple) authentication mechanism. You can use the context for that in a more meaningful (and abstract) way. In the case we are discussing, users can specify that an "authentication context" is related with trusting identities from an external IdP. In the future, we may even let users create their own "authentication context" by chaining authentication mechanisms. For instance, password + otp. IMO, is much better to use a single value like acme-loa-1, which means password + otp, than check for individual mechanisms. Regarding the value, I think we can use anything we want as along as all parties agree on the values being used.