jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-40) Define session-info like user identification for communication with oak-api
Date Thu, 31 May 2012 12:51:24 GMT

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

angela resolved OAK-40.
-----------------------

       Resolution: Fixed
    Fix Version/s: 0.3
    
> Define session-info like user identification for communication with oak-api
> ---------------------------------------------------------------------------
>
>                 Key: OAK-40
>                 URL: https://issues.apache.org/jira/browse/OAK-40
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core
>            Reporter: angela
>            Assignee: angela
>             Fix For: 0.3
>
>
> for the communication between oak-jcr and the api/spi to be defined we need 
> an interface that is obtained during the authentication process and is then used
> for all kind authorization throughout the lifetime of a given JCR session.
> in r1305860 i added an initial draft of such an interface (called SessionInfo for now).
> i will use this subtask to keep track of further refinement.
> currently that SessionInfo has the following methods:
> - getUserID: 
>   id of the user associated with original credentials.
> - getWorkspaceName: 
>   the workspace name as passed to the Repository.login or the default workspace name
if wspName was null.
> - getAttributeNames + getAttribute: 
>   attributes associated with that session. they may originate from the original credentials
or be 
>   implementation specific attributes as generated during the login process.
> - getRevision: 
>   initially the head revision of the mk. upon Session#refresh and any write operations
on the oak-api 
>   this revisionID is being updated to the latest version. 
>   we may discuss later on if it was desirable to create a JCR session for a specific
revisionID.
>   e.g. that could be passed with credential attributes.
> - dispose:
>   to indicate that this session info will no longer be used.
> currently i just added a dummy implementation to be able to move the
> Repository.login implementation down to oak-core.
> as soon as we have a clearer picture of how the communication between the jcr-layer
> and oak-api will look like that sessioninfo may contain additional 
> session internal information that may or may not be part of the interface: i could
> think of Subject, lock tokens...

--
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

        

Mime
View raw message