RE: Merging Sling API and Commons Auth API

Hi first of all: hello to all subscribers from my side :-) interface CredentialValidator +1 One issue remains: disposal of the Session placed into the AuthenticationInfo object by the validate method. But this can be solved, I am sure ... isn't this session just a session and hence

Re: Merging Sling API and Commons Auth API

On 3/16/10 4:17 PM, Mike Müller wrote: The case is what we discussed in [1]. There we came to the conclusion to use a RequestEventListener. Otherwise we have to add a lifecycle method like close or similar to the resource resolver or even to the CredentialValidator where it definitly makes no

[jira] Created: (SLING-1444) add an AuthenticationInfoPostProcessor service interface

add an AuthenticationInfoPostProcessor service interface Key: SLING-1444 URL: https://issues.apache.org/jira/browse/SLING-1444 Project: Sling Issue Type: Improvement

[jira] Created: (SLING-1445) store the AuthenticationInfo object in a request attribute

store the AuthenticationInfo object in a request attribute -- Key: SLING-1445 URL: https://issues.apache.org/jira/browse/SLING-1445 Project: Sling Issue Type: Improvement

[jira] Updated: (SLING-1444) add an AuthenticationInfoPostProcessor service interface

[ https://issues.apache.org/jira/browse/SLING-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1444: -- Component/s: Commons add an AuthenticationInfoPostProcessor service interface

[jira] Resolved: (SLING-1445) store the AuthenticationInfo object in a request attribute

[ https://issues.apache.org/jira/browse/SLING-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1445. --- Resolution: Fixed store the AuthenticationInfo object in a request attribute

[jira] Commented: (SLING-1445) store the AuthenticationInfo object in a request attribute

[ https://issues.apache.org/jira/browse/SLING-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846148#action_12846148 ] Justin Edelson commented on SLING-1445: --- done in r923991 and added to Authentication

[jira] Commented: (SLING-1444) add an AuthenticationInfoPostProcessor service interface

[ https://issues.apache.org/jira/browse/SLING-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846151#action_12846151 ] Justin Edelson commented on SLING-1444: --- done in r923990 and r923994. documented on

[jira] Resolved: (SLING-1444) add an AuthenticationInfoPostProcessor service interface

[ https://issues.apache.org/jira/browse/SLING-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1444. --- Resolution: Fixed add an AuthenticationInfoPostProcessor service interface

Hudson build is back to stable : sling-trunk-1.6 #336

See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/336/changes

Hudson build is back to stable : sling-trun k-1.5 » Apache Sling Launchpad Testing #637

See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/637/changes

Hudson build is back to stable : sling-trunk-1.5 #637

See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/637/changes

Build failed in Hudson: sling-contrib-1.5 #409

See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/409/ -- [...truncated 7059 lines...] br/ br/ br/

multi-workspace support in script resolution

Currently, although it's possible to log into different workspaces via AuthenticationInfo (even if httpauth and formauth don't support this); script resolution only happens against the default workspace. I don't see any reason for this restriction - it seems to me you should resolve scripts from