[
https://issues.apache.org/jira/browse/SLING-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292511#comment-13292511
]
Dragos Dascalita Haut commented on SLING-2504:
----------------------------------------------
I see. I personally though the /system/sling/form/login has been somehow
deprecated, seeing that it's not actually used in the samples, neither in the
Sling's main index.html page, when users click login.
I'm a bit confused though as to why would Sling expose 2 paths for the same
purpose. When should one approach be used and when should the other approach be
used ?
If the intent is to keep the 2 approaches then your first point makes sense and
adding an additional custom-login-sample would surely help.
> custom-login-form bundle is not working as expected
> ---------------------------------------------------
>
> Key: SLING-2504
> URL: https://issues.apache.org/jira/browse/SLING-2504
> Project: Sling
> Issue Type: Bug
> Components: Samples
> Affects Versions: Form Based Authentication 1.0.0
> Reporter: Dragos Dascalita Haut
> Labels: patch, samples
> Attachments: fixing_custom_login_form_sample.patch
>
>
> The custom-login-form doesn't affect the actual login UI.
> The bundle registers as a fragment for org.apache.sling.auth.form, while
> SelectorFormServlet is in org.apache.sling.auth.selector.
> The custom-login-form sample should register as a fragment for
> org.apache.sling.auth.selector.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
