You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/02/16 13:47:07 UTC
[jira] Closed: (SLING-105) JCR logon should be configurable
[ https://issues.apache.org/jira/browse/SLING-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-105.
-----------------------------------
Resolution: Won't Fix
This need not be implemented any more as microsling is replaced by Launchpad and full Sling
> JCR logon should be configurable
> --------------------------------
>
> Key: SLING-105
> URL: https://issues.apache.org/jira/browse/SLING-105
> Project: Sling
> Issue Type: Improvement
> Components: Repository
> Reporter: Michael Marth
> Priority: Minor
>
> Currently, the account (userid/password) with which microsling creates a JCR session can only be changed by a recompile. It would be nice if that was configurable instead. That would make the deployment easier.
> (Obviously, the password usually needs to be changed, but this is especially true when the JCR WebDAV drive needs to be exposed to the outside - which is the case the web application has static assets)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.