You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/08/08 11:47:00 UTC

[jira] [Closed] (SLING-11503) WebconsoleSecurityProvider: Force authentication against JCR

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

Joerg Hoh closed SLING-11503.
-----------------------------

> WebconsoleSecurityProvider: Force authentication against JCR
> ------------------------------------------------------------
>
>                 Key: SLING-11503
>                 URL: https://issues.apache.org/jira/browse/SLING-11503
>             Project: Sling
>          Issue Type: Task
>          Components: Extensions
>    Affects Versions: Web Console Security Provider 1.2.4
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>             Fix For: Web Console Security Provider 1.2.6
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> It should be possible to enforce an authentication against JCR even if SlingAuthentication is possible.
> Assume that Sling Authentication is using SAML, but it still must be possible to authenticate against the JCR using local users.
> This will just affect the authentication on the Webconsole!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)