[
https://issues.apache.org/jira/browse/SLING-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857944#action_12857944
]
Jason Rose commented on SLING-1472:
-----------------------------------
Looking into this more, it looks like the FormAuthServlet wasn't being picked
up on by Sling. That means that /system/sling/form/login was not a "safe" url
to hit, and was therefore being redirected to /system/sling/login. I changed
the superclass of the servlet and it looks like Sling is finding the servlet
again without issue. I included a patch with that change. If you all can find
a solution to the problem without changing the superclass, go ahead and do that
over this change.
> Form Auth seems unoperational
> -----------------------------
>
> Key: SLING-1472
> URL: https://issues.apache.org/jira/browse/SLING-1472
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Environment: sling trunk -r930334 on fuse 4.2
> Reporter: Jason Rose
> Attachments: formauth_superclass_patch.patch
>
>
> Installing bundle
> mvn:org.apache.sling/org.apache.sling.formauth/0.9-SNAPSHOT doesn't seem to
> actually provide any functionality.
> curl http://localhost:8181/system/sling/form/login returns a 404.
> The authentication handler itself doesn't seem to provide any login or logout
> support; if I post to /j_security_check with the correct credentials, the
> basic auth handler handles it. I don't know if the form auth code is even
> running at all. Calling /system/sling/logout pops up the basic challenge
> modal in my browser.
> It looks like there was a Sakai bug raised about this a while ago, and they
> fixed it. I don't know if the code was backported, or what.
> http://jira.sakaiproject.org/browse/KERN-716
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
