[
https://issues.apache.org/jira/browse/SLING-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829780#action_12829780
]
Matt Torrenzano commented on SLING-1116:
----------------------------------------
To update, I was able to resolve all of my dependencies . Day just produced a
product upgrade to CQ 5.3 that has an updated instance of Felix.
For anyone that is try to implment with Day with the
update2_org.apache.sling.cookieauth.zip , here are the details:
org.apache.sling.commons.auth was taken care of in the Apache CQ 5.3 upgrade.
I downloaded the source of org.apache.sling.jcr.jackrabbit-server and generated
that bundle. There were only two packages that I couldn't resolve:
org.apache.sling.jcr.base and org.apache.jackrabbit.api.jsr283.*
I downloaded the org.apache.sling.jcr.base code, bundled it, and deployed ito
Felix. Base needed the jsr283.security file.
I downloaded the org.apache.jackrabbit.api v1.6.0 jar and "bundlized" it via
bnd and installed that into Felix.
All my dependencies have now been resolved. So to recap, to get all of the
dependencies resolved, you need to include the following bundles/jars
org.apache.jackrabbit.api (1.6.0)
org.apache.sling.jcr.base (2.0.5.SNAPSHOT)
org.apache.sling.jcr.jackrabbit.server (2.0.5.SNAPSHOT)
org.apache.sling.commons.auth.spi,version=1.0.0 from
org.apache.sling.commons.auth (100) <- Missing from Day CQ 5.2.1 but taken care
of in Day CQ 5.3
My next few steps will be to try and test your functionality out while
integrated with Day CMS.
> FORM Based Authentication
> -------------------------
>
> Key: SLING-1116
> URL: https://issues.apache.org/jira/browse/SLING-1116
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Eric Norman
> Assignee: Felix Meschberger
> Attachments: org.apache.sling.cookieauth.zip,
> org.apache.sling.sessionauth.zip, SLING_1116_jackrabbit_server_patch.txt,
> update2_org.apache.sling.cookieauth.zip,
> updated_org.apache.sling.cookieauth.zip
>
>
> This is a new bundle that provides an implementation of forms based
> authentication for sling.
> The login/logout servlets from the org.apache.sling.commons.auth are used.
> The AuthenticationHandler will use http basic auth credentials if they are on
> the request, otherwise it will use the user/pwd posted from the login form.
> The login form html is generated by a set of scripts
> 1. login.html.esp - full login page (includes login_body.html.esp for the
> form markup)
> 2. login_body.html.esp - just the login form, which may be useful for
> drawing the login form for an ajax context
> 3. loginError.html.esp - full login-error page
> 4. loginError_body.html.esp - just the login-error form, for login error in
> ajax context
> The above scripts are included as bundle-resources @
> /libs/sling/servlet/default
> The bundle also has a couple of test scripts to show some examples of usage:
> 1. loginTest.html.esp - shows who is logged in and links to login or logout
> 2. loginTest2.html.esp - shows how a script can check permissions and show a
> login page if the anonymous user doesn't have permission to see the page,
> Some examples of usage are:
> 1. http://host:port/path/to/node.login.html - show the login page and then
> goto http://host:port/path/to/node after authenticated
> 2. http://host:port/path/to/node.login.html?s=.edit.html - show the login
> page and then goto http://host:port/path/to/node.edit.html after
> authenticated
> 3. http://host:port/system/sling/logout - invalidate the session and switch
> back to anonymous user
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
