Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Fri, 2 Jun 2017 09:35:04 +0000 (UTC)
From: "Robert Munteanu (JIRA)" <jira@apache.org>
To: oak-issues@jackrabbit.apache.org
Message-ID: <JIRA.13067692.1493387101000.350140.1496396104315@Atlassian.JIRA>
In-Reply-To: <JIRA.13067692.1493387101000@Atlassian.JIRA>
References: <JIRA.13067692.1493387101000@Atlassian.JIRA> <JIRA.13067692.1493387101748@jira-lw-us.apache.org>
Subject: [jira] [Commented] (OAK-6144) ExternalIdentity should have a method
 indicating if an identity is actually active
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Jun 2017 09:35:11 -0000


    [ https://issues.apache.org/jira/browse/OAK-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034387#comment-16034387 ] 

Robert Munteanu commented on OAK-6144:
--------------------------------------

[~baedke] - good news, glad to hear that it works

> ExternalIdentity should have a method indicating if an identity is actually active
> ----------------------------------------------------------------------------------
>
>                 Key: OAK-6144
>                 URL: https://issues.apache.org/jira/browse/OAK-6144
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: auth-external
>            Reporter: Manfred Baedke
>            Assignee: Manfred Baedke
>         Attachments: oak-6144-1.patch
>
>
> The interface ExternalIdentityProvider currently offers the method getIdentity(ExternalIdentityRef) to resolve a reference to an external Identity, but there is no way to tell if the external identity is considered active by the identity provider. The ability to resolve the reference doesn't mean that the resulting identity may actually be used for authentication or authorization.
> If ExternaIIdentity isn't able to express this difference, it's hard to come up with a sensible implemenation of e.g. SynchronizationMBean#purgeOrphanedUsers(), because the ability to resolve a reference to an external identity doesn't mean that the corresponding Oak user is still valid.
> A new method ExternalIdentiy#isActive() would allow us to clearly define the notion of an "orphaned user".


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)