[
https://issues.apache.org/jira/browse/SLING-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647045#comment-15647045
]
Bertrand Delacretaz commented on SLING-6219:
--------------------------------------------
Both cases, with or without a space after the encoding, parse the same, with
separate values for the password encoding and the password itself - so
{noformat}{SHA-256}dc460da4{noformat} is not a single value, it's two tokens
for the repoinit parser.
I initially implemented it in this way to avoid making the string definition in
the parser more complex (to accept curly brackets) and I think it's good to
specify how repoinit parses the encoding part anyway as that's a generic
concept that does necessarily need to be tied to Oak.
I have modified the tests in revision 1768648 to explicitly test that the
encoding and password are correctly split by the parser.
> 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)
