[
https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-5274:
---------------------------------------
Attachment: SLING-5274-bertrand.patch
Creating the SlingRequestProgressTracker in handleSecurity is actually easy,
here's a patch that implements that (SLING-5274-bertrand.patch).
[~cziegeler] will this new patch also be obsolete with the new whiteboard stuff
that you mention? Otherwise we can apply it, it already provides minimal info
about authentication:
{code}
24 TIMER_START{handleSecurity}
2265 TIMER_END{2239,handleSecurity} authenticator
org.apache.sling.auth.core.impl.SlingAuthenticator@355f6004 returns true
{code}
> 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-bertrand.patch, 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)
