[
https://issues.apache.org/jira/browse/SLING-12714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941037#comment-17941037
]
Oliver Lietz commented on SLING-12714:
--------------------------------------
adaptTo() 2018: [Modern authentication in Sling with OpenID Connect and
Keycloak|https://adapt.to/2018/schedule/modern-authentication-in-sling-with-openid-connect-and-keycloak]
> Oidc Authentication Handler
> ---------------------------
>
> Key: SLING-12714
> URL: https://issues.apache.org/jira/browse/SLING-12714
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Nicola Scendoni
> Priority: Minor
> Fix For: OAuth Client 0.1.2
>
>
> {*}Description:{*}{*}{*}
> Apache Sling currently provides an *OAuth 2 client*, but it is *not an
> authentication handler*. This means that while applications can use OAuth 2
> for authorization, there is no built-in mechanism to handle user
> authentication via OpenID Connect (OIDC). Given the widespread adoption of
> OIDC for authentication, adding support for an *OIDC Authentication Handler*
> would greatly enhance Sling’s authentication capabilities.
>
> {*}Feature Request:{*}{*}{*}
> Develop a pluggable *OIDC Authentication Handler* that enables authentication
> via OpenID Connect providers (e.g., Google, Azure AD, Keycloak, Okta).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
