jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pontus Amberg (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3188) Try JACC / JSR-115 to get Subject in RepositoryImpl
Date Mon, 26 Dec 2011 17:06:31 GMT

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

Pontus Amberg updated JCR-3188:

    Attachment: JACC_patch2.diff.zip

Updated the patch so that it now also works for Glassfish. Had to move the Subject lookup
before extendAuthentication() to prevent AnonymousPrincipal to be added to the subject even
if the subject already is authenticated in Glassfish. If anonymous is added SimpleAccessManager
will only allow reads from the repository.
> Try JACC / JSR-115 to get Subject in RepositoryImpl
> ---------------------------------------------------
>                 Key: JCR-3188
>                 URL: https://issues.apache.org/jira/browse/JCR-3188
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.3.5
>         Environment: JCA Jackrabbit, JEE container, preauthenticated subject
>            Reporter: Pontus Amberg
>         Attachments: JACC_patch2.diff.zip
> The extendAuthentication() method in RepositoryImpl could try to use JACC /JSR-115 (
http://jcp.org/en/jsr/detail?id=115 ) to get a preauthenticated subject if Subject.getSubject()
fails ( see JCR-1584 ).
> This seems to make it possible in for example JBoss to get a session without specifying
any credentials in the repository.login() method if the user already is authenticated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message