You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2010/07/14 02:06:54 UTC

[jira] Commented: (SLING-608) Provide Authentication Control

    [ https://issues.apache.org/jira/browse/SLING-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888117#action_12888117 ] 

Justin Edelson commented on SLING-608:
--------------------------------------

Closing this issue out... Sling now supports both rich user authentication via Jackrabbit extensions and versioning via the post servlet.

> Provide Authentication Control
> ------------------------------
>
>                 Key: SLING-608
>                 URL: https://issues.apache.org/jira/browse/SLING-608
>             Project: Sling
>          Issue Type: Improvement
>          Components: Documentation, JCR, Launchpad
>    Affects Versions: Launchpad Webapp 3
>            Reporter: Marvin Phelps
>
> Sling sits atop a content repository - so there should be better examples of how to post versions and list versions. (mix:versionable). I managed to find out how to do this using the Day notes application. Secondly, it's now apparent to me that the LaunchPad webapp is using Jackrabbit's SimpleLoginModule and by default it allows access for every user: even http://doodoo:poopoo@localhost:8888/ Sling needs to have some authentication strategy built-in. With this stuff provided in Launchpad, Sling would be more usable out of the box.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.