[ 
http://jira.magnolia.info/browse/MAGNOLIA-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Bracher reopened MAGNOLIA-2313:
---------------------------------------


Thanks it makes a lot of sense. We are now ready to release 3.6.2 with some 
important bugfixes we want to ship as soon as possible. Unfortunately we have 
some dependencies to this class in other EE modules and testing it now would 
requires a lot of extra work.

So we have to skip that change for 3.6.2 but will re-add it immediately in both 
the 3.6 branch and 3.7 trunk.

I hope you understand that we can't risk to break other EE modules without 
double checking it first.

> JcrAuthorizationModule should not extend JCRAuthenticationModule
> ----------------------------------------------------------------
>
>                 Key: MAGNOLIA-2313
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2313
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.6.1
>            Reporter: Fabrizio Giustina
>            Assignee: Fabrizio Giustina
>            Priority: Critical
>             Fix For: 3.6.2
>
>
> ... or at least it shouldn't call login() in the JCRAuthenticationModule.
> The problem is that JcrAuthorizationModule should be usable to handle jcr 
> authorization (expand groups and roles to ACLs), regardless of the 
> authentication method used. But if you try to supply a different 
> Authorization module, at least if this module uses different callbacks from 
> the JcrAuthenticationModule, the login() method in the 
> JCRAuthenticationModule will never pass.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to