[
https://issues.apache.org/jira/browse/SLING-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829221#action_12829221
]
Matt Torrenzano commented on SLING-1116:
----------------------------------------
Eric/Felix,
Hello, I am trying to implement your session authentication solution for
deployment within our Day CQ 5 CMS custom solution. I downloaded the source
code, ran a maven package and deployed it into our Apache Felix OSGI container.
Unfortuantely I am getting two "Cannot be resolved" import issues:
!! org.apache.sling.commons.auth.spi,version=1.0.0 -- Cannot be resolved
!! org.apache.sling.jcr.jackrabbit.server.security,version=2.0.0 from -- Cannot
be resolved
I downloaded the source code for "auth.spi" from Apache, created a bundle and
deployed that into Felix; however, I am still having trouble producing a bundle
for the jackrabbit dependency. There's a POM file located at
org\apache\sling\jcr\jackrabbit-server however when I deploy that bundle I get
another 15 cannot resolve imports from this bundle.
Instead of going down the long path for trying to resolve all of the
dependencies, is there any smaller bundle or alternate suggestion for trying to
get the bundle to resolve correctly? We're using Day's CQ5 product which
includes an instance of Apache Felix.
> 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.
