You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/01/18 15:32:39 UTC

[jira] [Resolved] (SLING-5217) Verify if login failures to resource providers are handled correctly

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

Robert Munteanu resolved SLING-5217.
------------------------------------
    Resolution: Fixed
      Assignee: Robert Munteanu

The code looks good to me and I've verified the behaviour using a MongoDB provider with the patches from SLING-5437.

Considering fixed.

> Verify if login failures to resource providers are handled correctly
> --------------------------------------------------------------------
>
>                 Key: SLING-5217
>                 URL: https://issues.apache.org/jira/browse/SLING-5217
>             Project: Sling
>          Issue Type: Sub-task
>          Components: ResourceResolver
>            Reporter: Carsten Ziegeler
>            Assignee: Robert Munteanu
>             Fix For: Resource Resolver 1.3.0
>
>
> If a resource provider is marked as required auth, then the login is performed on creation of the resource resolver impl - if it fails, not RR is created. This is correct.
> For providers marked as lazy auth, if login fails they are not tried again and they are treated as if auth was successful, but all get methods return null and all set methods either throw or do nothing. I haven't verified this in all places yet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)