[
https://issues.apache.org/jira/browse/SLING-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646870#comment-15646870
]
Bertrand Delacretaz edited comment on SLING-6219 at 11/8/16 9:36 AM:
---------------------------------------------------------------------
[~bdelacretaz] Hmm, but
{code}
{SHA-256}dc460da4....
{code}
is a single value, the password - it just happens to have an encoding as part
of the value at the front, but looking at the test files ,there is
{noformat}
create user userD with password
{SHA-256}dc460da4ad72c482231e28e688e01f2778a88ce31a08826899d54ef7183998b5
create user userE with password {someEncoding} afdgwdsdf
{noformat}
So I'm really wondering about the second case. The first one works with just
having a single parameter for the password and once Oak supports setting this,
we don't need to change the grammar but just do the right user creation call
was (Author: cziegeler):
[~bdelacretaz] Hmm, but
{code}
{SHA-256}dc460da4....
{code}
is a single value, the password - it just happens to have an encoding as part
of the value at the front, but looking at the test files ,there is
{code}
create user userD with password
{SHA-256}dc460da4ad72c482231e28e688e01f2778a88ce31a08826899d54ef7183998b5
create user userE with password {someEncoding} afdgwdsdf
[code}
So I'm really wondering about the second case. The first one works with just
having a single parameter for the password and once Oak supports setting this,
we don't need to change the grammar but just do the right user creation call
> Allow to create users with repoinit
> -----------------------------------
>
> Key: SLING-6219
> URL: https://issues.apache.org/jira/browse/SLING-6219
> Project: Sling
> Issue Type: New Feature
> Components: JCR, Repoinit
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Repoinit Parser 1.0.4, Repoinit JCR 1.0.4
>
>
> it seems it's not possible to create a user through the repoinit.
> This would be very useful for sample apps and testing. For example, the
> slingshot sample app currently needs an admin user to create the sample
> user accounts. And therefore slingshot needs to be in the whitelist for
> admin usage - which is not a good thing
> I suggest we add:
> create user {name}
> create user {name} {password}
> delete user {name}
> If no pw is provided for create user, we create a random pw
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
