[
https://issues.apache.org/jira/browse/SLING-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rose updated SLING-1472:
------------------------------
Attachment: formauth_superclass_patch.patch
I think I've fixed the issue. The formauth just extended servlet, and
switching its parent class to a sling servlet caused the servlet to be found
again. I don't know if you'd rather keep api dependencies as simple as
possible, but this completely fixes the problem for me.
I also have a fix in here because the form auth handler wasn't logging one of
the properties. I don't know if you want it to be in a different issue, but
it's very minor so I put it here.
> 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
