[
https://issues.apache.org/jira/browse/JSPWIKI-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033952#comment-18033952
]
Alex O'Ree commented on JSPWIKI-1176:
-------------------------------------
i think the "fix" for this is to provide some way to map external roles
(tomcat, ldap, etc) to jspwiki roles via configuration, then edit
WebContainerLoginModule.java to somehow obtain the mappings config, then check
request.IsUserInRole(remoteRole), then add the jspwiki role as needed.
sounds easy in theory, however there's no directly access to the wiki engine
nor configuration from that class currently
> 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
>
> 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)
