jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-72) Session.impersonate non-functional
Date Fri, 18 Mar 2005 14:13:21 GMT
     [ http://issues.apache.org/jira/browse/JCR-72?page=history ]
     
Stefan Guggisberg closed JCR-72:
--------------------------------

    Resolution: Fixed

'impersonation' process is now delegated to LoginModule implementation;
Subject of impersonating session is passed on to LoginModule as attribute
of credentials

fixed in rev. 158072

> Session.impersonate non-functional
> ----------------------------------
>
>          Key: JCR-72
>          URL: http://issues.apache.org/jira/browse/JCR-72
>      Project: Jackrabbit
>         Type: Bug
>   Components: API
>  Environment: Jackrabbit SVN Rev. 157914
>     Reporter: Felix Meschberger
>     Assignee: Stefan Guggisberg
>     Priority: Critical

>
> Currently SessionImpl.impersonate simply calls Repository.login with the given credentials
and the workspace name of the session. If the credentials are incomplete in that the password
is missing, the method throws a "LoginException: Failed to authenticate userID", which is
actually a misleading text, as the reason is not failure to authenticate userID but at best
that the session has not enough access rights to impersonate as userID.
> For my application, it is crucial, that Session.impersonate is implemented in the sense
that this method allows creation of a session with password-less credentials. I accept this
method to fail, but it should fail with a correct message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message