Hi
> Am 14.01.2015 um 04:01 schrieb Alexander Klimetschek :
>
> On 12.01.2015, at 14:53, Alexander Klimetschek wrote:
>> Ack, sounds good. I created https://issues.apache.org/jira/browse/SLING-4301
>
> I attached a patch.
>
> But while testing it, I had a problem, see
> https://issues.apache.
On 12.01.2015, at 14:53, Alexander Klimetschek wrote:
> Ack, sounds good. I created https://issues.apache.org/jira/browse/SLING-4301
I attached a patch.
But while testing it, I had a problem, see
https://issues.apache.org/jira/browse/SLING-4301?focusedCommentId=14276415&page=com.atlassian.jira.
On 12.01.2015, at 02:53, Felix Meschberger wrote:
>
> IIRC we have been discussing that before … Not sure what the resolution was
> and I actually was under impression we agreed to do it. Maybe it just fell
> off the trenches.
>
> Yes, I think a new constant
>
>> JcrResourceContstants.AUTHENT
Hi
IIRC we have been discussing that before … Not sure what the resolution was and
I actually was under impression we agreed to do it. Maybe it just fell off the
trenches.
Yes, I think a new constant
> JcrResourceContstants.AUTHENTICATION_INFO_SESSION_LOGOUT =
> „user.jcr.session.logout“;
So
hi Alex,
is there any JIRA issue I can watch ?
regards
antonio
On Jan 10, 2015, at 3:54 AM, Alexander Klimetschek wrote:
> Hi,
>
> one of the options in a Sling Authentication handler is to create the session
> itself and pass it via "user.jcr.session" [1] in the AuthenticationInfo. But
> t
Hi,
one of the options in a Sling Authentication handler is to create the session
itself and pass it via "user.jcr.session" [1] in the AuthenticationInfo. But
this session is never closed automatically by Sling, forcing you to also write
yet-another ServletFilter that closes the session at the
