[ 
https://issues.apache.org/jira/browse/JSPWIKI-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated JSPWIKI-1375:
------------------------------------
    Labels: pull-request-available  (was: )

> The OpenID Connect login only works with Keycloak and should work with any 
> OpenID Connect provider, as Google or Azure
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JSPWIKI-1375
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-1375
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Authentication & Authorization
>            Reporter: Arturo Bernal
>            Priority: Major
>              Labels: pull-request-available
>
> The OpenID Connect login added for JSPWIKI-94 uses the Keycloak client of 
> pac4j and reads the roles with the Keycloak roles generator, so it works only 
> with Keycloak. Most providers, as Google and Microsoft Entra ID (Azure), 
> speak standard OpenID Connect, and the module should work with them.
> Proposal: use the generic OpenID Connect client of pac4j, configured with the 
> discovery URL of the provider, and make these configurable in 
> jspwiki-oidc.properties:
> - the claim used as the name of the user (preferred_username by default, then 
> email),
> - the claim that has the roles, searched in the claims of the user profile 
> and of the access token when it is a JWT, with a dotted path for nested 
> claims (realm_access.roles for Keycloak, roles for the application roles of 
> Azure),
> - an optional mapping from the values of that claim to the roles of the wiki, 
> for the providers that send identifiers instead of names.
> Google does not send roles, so its users are authenticated users of the wiki, 
> and the administrators can be defined with groups of the wiki.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to