[
https://issues.apache.org/jira/browse/SLING-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031217#comment-18031217
]
Eric Norman commented on SLING-10606:
-------------------------------------
[~rombert] I've attempted to provide a solution to this before releasing the
2.x version of the auth.form bundle. There were changes to 4 bundles which I
provided in separate pull requests that are linked in subtasks. Please advise
if the solution is acceptable to you or if there are any changes you would like
to see.
> Default login page should not reference content from the starter.content
> module
> -------------------------------------------------------------------------------
>
> Key: SLING-10606
> URL: https://issues.apache.org/jira/browse/SLING-10606
> Project: Sling
> Issue Type: Improvement
> Components: Authentication, Starter
> Reporter: Robert Munteanu
> Assignee: Eric Norman
> Priority: Major
> Fix For: Form Based Authentication 1.0.26, Starter Content
> 1.0.18, Starter Content 2.0.2, Form Based Authentication 2.0.0
>
> Attachments: login-form-without-starter-content.png,
> resources-not-found-without-starter-content.png
>
>
> The default login form references images and styles from the starter.content.
> We should avoid that, since the default login form can be deployed in other
> scenarios as well. Instead, we should:
> - provide a standalone login page for the o.a.s.auth.form bundle
> - move the current login form to o.a.s.starter.content bundle
> The intent is to have a good-looking form for the starter content but also
> one that does not look broken for auth.form.
> We should also add an HTML comment to the default login form pointing to
> customisation possibilites.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
