[
https://issues.apache.org/jira/browse/SLING-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292601#comment-13292601
]
Eric Norman commented on SLING-2504:
------------------------------------
Well, the o.a.s.auth.selector technique is really only useful if you intend to
support forms based authentication and OpenID authentication and you want the
user to be able to choose which of those two to use. It provides a login page
that merges the login forms of the auth.form and auth.openid auth bundles into
one page.
If your application doesn't need or want to support OpenID auth, then you could
uninstall the auth.selector and auth.openid bundles. If you uninstall those
bundles, then the login link in the launchpad main page would go to the next
available auth handler (ordered by the service ranking) which could be the one
in the auth.form bundle (or some other custom auth handler that you have
installed).
> 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
