[Bug 55477] Add a solution to map an realm name to a security role

https://bz.apache.org/bugzilla/show_bug.cgi?id=55477 Bug 55477 depends on bug 63636, which changed state. Bug 63636 Summary: Context#findRoleMapping() never called in StandardWrapper#findSecurityReference() https://bz.apache.org/bugzilla/show_bug.cgi?id=63636 What|Removed

[Bug 55477] Add a solution to map an realm name to a security role

https://bz.apache.org/bugzilla/show_bug.cgi?id=55477 Michael Osipov changed: What|Removed |Added CC||micha...@apache.org Depends o

[Bug 55477] Add a solution to map an realm name to a security role

https://bz.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #10 from Mark Thomas --- Context.addRoleMapping() does most of what is required (at least it will after bug 63636 is fixed). Just need a way to add the roles via configuration rather than JMX / code. -- You are receiving this mail

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 Stefan Mayr changed: What|Removed |Added Attachment #30759|0 |1 is obsolete|

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #8 from Stefan Mayr --- Christopers version would be like this: -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe,

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #7 from Stefan Mayr --- Created attachment 30788 --> https://issues.apache.org/bugzilla/attachment.cgi?id=30788&action=edit Edition with inline configuration for the role mapping I added the possibility to configure the mappi

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #6 from Stefan Mayr --- I thought about defining a custom ressource to make an inline configuration possible without messing with the Digester rules. So I searched and found http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #5 from Christopher Schultz --- I'm not sure I understand your statement. Can you explain further? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #4 from Stefan Mayr --- Usual bean settings (like for a custom resource) which can be expressed in sub xml elements are attributes in the server.xml file. configuration in beans: value1 value2 Tomcat: map="???" Any

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #3 from Christopher Schultz --- Yeah, you can access sub-elements (we use Digester, so it just needs to be configured, but I'd prefer not to modify the digester configuration if it's not necessary). I was a little worried about

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #2 from Stefan Mayr --- Should be possible. Where to find the rules about the security role naming conventions? The parsing of such an attribute might be tricky. Although this could be controlled by extra parameters (delimiter,a

[Bug 55477] Add a solution to map an realm name to a security role

https://issues.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #1 from Christopher Schultz --- I haven't looked at the patch yet, but I wonder if configuring the wrapper-realm could be done directly in the context.xml like this: ... Thoughts? -- You are receiving this mail because: