[
https://issues.apache.org/jira/browse/SLING-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241773#comment-16241773
]
angela edited comment on SLING-7226 at 11/7/17 10:04 AM:
---------------------------------------------------------
[~marett], the API contract doesn't mandate any specific format and leaves it
to the implementation to reject invalid paths. So, I wouldn't make any attempt
to perform the validation yourself.
regarding userID: I don't recall having any kind of limitations here but I
neither recall explicitly testing if it works. Again I would suggest to leave
the validation to the implementation.
was (Author: anchela):
[~marett], the API contract doesn't mandate any specific format and leaves it
to the implementation to reject invalid paths. So, I wouldn't make any attempt
to perform the validation yourself.
regarding userID: I don't recall having any kind of limitations here but I
neither recall explicitly testing if it works.
> Repo Init: allow to pass intermediate path upon creating service user
> ---------------------------------------------------------------------
>
> Key: SLING-7226
> URL: https://issues.apache.org/jira/browse/SLING-7226
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: angela
>
> [~marett], [~bdelacretaz], if I am not mistaken it is currently not possible
> to pass the second parameter 'intermediatePath' when creating a service user
> using the repo-init.
> In the Jackrabbit {{UserManager}} API the call looks as follows:
> {code}
> UserManager.createSystemUser(String userID, String intermediatePath)
> {code}
> I would appreciate if both params would be respected by the repo-init and I
> don't think it should be a big deal adding this.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
