[
https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134105#comment-15134105
]
Carsten Ziegeler commented on SLING-5274:
-----------------------------------------
I think in general this makes totally sense - but I'm not sure if the current
approach is the best, especially if we think about moving to the http
whiteboard implementation (which we should do soon)
Context#handleSecurity is called "before" Sling, that's why this patch does
this rather ugly passing around of the request progress tracker. I think we
should try to think about a cleaner solution
> Include authentication in RequestProgressTracker
> ------------------------------------------------
>
> Key: SLING-5274
> URL: https://issues.apache.org/jira/browse/SLING-5274
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Alexander Klimetschek
> Attachments: SLING-5274.patch
>
>
> The request progress tracker only starts with the sling filters, after the
> sling authentication ran through. Since authentication steps can be complex
> with multiple handlers (just like filters) and can have a major performance
> impact (custom auth handlers, slow resource resolver login) it would be very
> useful to include it with detailed information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
