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

Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2022/09/26 07:28:00 UTC

[jira] [Resolved] (SLING-11598) Don't reactivate authenticator on configuration change

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

Carsten Ziegeler resolved SLING-11598.
--------------------------------------
    Resolution: Fixed

https://github.com/apache/sling-org-apache-sling-auth-core/commit/fb8d4c91037e041206c42e2f053ecf410f340fee

> Don't reactivate authenticator on configuration change
> ------------------------------------------------------
>
>                 Key: SLING-11598
>                 URL: https://issues.apache.org/jira/browse/SLING-11598
>             Project: Sling
>          Issue Type: Improvement
>          Components: Authentication
>    Affects Versions: Auth Core 1.5.6, Auth Core 1.5.8
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Auth Core 1.5.10
>
>
> Due to some refactorings of auth core, the Sling Authenticator is currently re-registered if its configuration changes. This has unwanted rippling effects on all components depending on the authentication support service.
> Configuration changes should be handled via modified events internally



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