[
https://issues.apache.org/jira/browse/OAK-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905093#comment-16905093
]
Joseph Rignanese edited comment on OAK-8537 at 8/12/19 11:31 AM:
-----------------------------------------------------------------
[~angela], [~dominique.jaeggi], [~stillalex] keen to know your thoughts on this.
Having a set of regex to evaluate against the user ID, when determining if the
user's password can expire should meet all of the use cases above.
was (Author: [email protected]):
[~angela], [~dominique.jaeggi], keen to know your thoughts on this.
Having a set of regex to evaluate against the user ID, when determining if the
user's password can expire should meet all of the use cases above.
> Password expiry exclusion list
> ------------------------------
>
> Key: OAK-8537
> URL: https://issues.apache.org/jira/browse/OAK-8537
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Joseph Rignanese
> Priority: Major
>
> Currently when the password expiry functionality is configured there is no
> way to exclude specific users from this expiration.
> This can be a little bit of an impediment for implementing a password expiry
> policy as it can affect key system accounts.
> Some examples of users that would be affected, but implementations may want
> to be excluded are:
> # Sling content distribution users
> # Replication users (Adobe AEM)
> # Screens users (Adobe AEM)
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
