I try to find out a way to configure @OpenIdAuthenticationMechanismDefinition in a more dynamic way.
Of course you can provide the values for OPENID_PROVIDERURI, the OPENID_CLIENTID or the OPENID_CLIENTSECRET by defining the corresponding environment variables or use EL and a config CDI Bean.
But it seems that more complex params like scope or extraParameters can only be hard coded in @OpenIdAuthenticationMechanismDefinition.
This means you can't write an interoperable application using different OpenID providers. You have to implement several Beans for each Provider and encapsulate them in separate libraries which you can than bundle with your application.
https://stackoverflow.com/questions/76468527/how-to-use-el-in-extraparameters-attribute-of-the-openidauthenticationmechanism
Did I miss something here or is this an know issue?
Concrete we need to develop an application that runs in produciton with ForgeRock and in Test with Auth0. Both providers need custom configuration in the scope and extraParameters
I try to find out a way to configure
@OpenIdAuthenticationMechanismDefinitionin a more dynamic way.Of course you can provide the values for
OPENID_PROVIDERURI, theOPENID_CLIENTIDor theOPENID_CLIENTSECRETby defining the corresponding environment variables or use EL and a config CDI Bean.But it seems that more complex params like
scopeorextraParameterscan only be hard coded in @OpenIdAuthenticationMechanismDefinition.This means you can't write an interoperable application using different OpenID providers. You have to implement several Beans for each Provider and encapsulate them in separate libraries which you can than bundle with your application.
https://stackoverflow.com/questions/76468527/how-to-use-el-in-extraparameters-attribute-of-the-openidauthenticationmechanism
Did I miss something here or is this an know issue?
Concrete we need to develop an application that runs in produciton with ForgeRock and in Test with Auth0. Both providers need custom configuration in the
scopeandextraParameters