[
https://issues.apache.org/jira/browse/JSPWIKI-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034196#comment-18034196
]
Alex O'Ree commented on JSPWIKI-1176:
-------------------------------------
i've made some progress with this.
was able to get remote roles attached to internal jspwiki roles, however the
AllPermission thing still isn't working as expected. It has also introduced a
new bug, the login display name is randomly a role or the user name
!image-2025-10-30-10-46-44-578.png!
still fighting with it, but at least it's progress. solution enables an
aliasing type of mechanism that enables mapping externally defined roles/group
membership/attributes etc to jspwiki specific roles
> Admin and Autenticated roles hard coded
> ---------------------------------------
>
> Key: JSPWIKI-1176
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1176
> Project: JSPWiki
> Issue Type: Bug
> Components: Authentication & Authorization
> Affects Versions: 2.11.3
> Environment: wildfly-26.1.2.Final
> Reporter: Jürgen Weber
> Priority: Minor
> Attachments: image-2025-10-30-10-46-44-578.png
>
>
> With container manged auth in JBoss EAP I had changed the Admin and
> Autenticated role names to role names from our AD.
> (changed jspwiki.policy and web.xml)
> Login and trying to edit failed then with the infamous Sorry, but you are not
> allowed to do that error page.
> I then used a JBoss role mapper from our roles to Admin and Autenticated and
> things worked.
> Looks like the Admin and Autenticated roles are somewhere hard coded (in .js
> ?).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
