[
https://issues.apache.org/jira/browse/JCR-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamil updated JCR-3922:
-----------------------
Description:
When you try assign principal based privilege to an admin, an exception is
thrown:
{noformat}
Invalid principal. Expected:
org.apache.jackrabbit.core.security.user.UserImpl$NodeBasedAdminPrincipal
{noformat}
Maybe "You cannot add entry for the principal "FOO" because this
JackrabbitAccessControlList is for principal BAZ" would be more meaningful?
And by the way - why addEntry takes principal, if JackrabbitAccessControlList
was already created for this specific principal and you know exactly which one
(line 181 in
org.apache.jackrabbit.core.security.authorization.principalbased.ACLTemplate)?
was:
When you try assign principal based privilege to an admin, an exception is
thrown:
{noformat}
Invalid principal. Expected:
org.apache.jackrabbit.core.security.user.UserImpl$NodeBasedAdminPrincipal
{noformat}
Maybe "You cannot assign privilege to admin account" would be more meaningful?
> Change exception message
> ------------------------
>
> Key: JCR-3922
> URL: https://issues.apache.org/jira/browse/JCR-3922
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Kamil
> Priority: Minor
>
> When you try assign principal based privilege to an admin, an exception is
> thrown:
> {noformat}
> Invalid principal. Expected:
> org.apache.jackrabbit.core.security.user.UserImpl$NodeBasedAdminPrincipal
> {noformat}
> Maybe "You cannot add entry for the principal "FOO" because this
> JackrabbitAccessControlList is for principal BAZ" would be more meaningful?
> And by the way - why addEntry takes principal, if JackrabbitAccessControlList
> was already created for this specific principal and you know exactly which
> one (line 181 in
> org.apache.jackrabbit.core.security.authorization.principalbased.ACLTemplate)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
