https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
Mark Thomas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #22 from Martin bestandig ---
Dellet
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
Mark Thomas changed:
What|Removed |Added
Product|Tomcat 7|Tomcat 8
Version|trunk
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #20 from Christopher Schultz ---
(In reply to Michael Osipov from comment #19)
> (In reply to Christopher Schultz from comment #18)
> > How applicable is in web.xml, here?
>
> As far as I know, this is per-servlet which can be
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #19 from Michael Osipov ---
(In reply to Christopher Schultz from comment #18)
> How applicable is in web.xml, here?
As far as I know, this is per-servlet which can be very tedious and cannot be
externalized.
> (In reply to
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #18 from Christopher Schultz ---
How applicable is in web.xml, here?
(In reply to Stefan Mayr from comment #16)
> After a quick look into Michael's documentation I'm only concerned about the
> placement of the default config in
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #17 from Michael Osipov ---
(In reply to Stefan Mayr from comment #16)
> At the time I wrote this realm I did not know of any other role name mapping
> add-ons. I'm not sure if Michael's solution already was public. Although I
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #16 from Stefan Mayr ---
At the time I wrote this realm I did not know of any other role name mapping
add-ons. I'm not sure if Michael's solution already was public. Although I
don't need it anymore the use case is still valid.
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #15 from Christopher Schultz ---
(In reply to Michael Osipov from comment #14)
> (In reply to Christopher Schultz from comment #13)
>
> I don't like the approach tying the mapping to the realm as depicted by you
> or Stefan.
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #14 from Michael Osipov ---
(In reply to Christopher Schultz from comment #13)
> (In reply to Michael Osipov from comment #12)
> > I am not convinced by that approach.
>
> Which approach? RealmBase? Context.addRoleMapping?
>
> >
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #13 from Christopher Schultz ---
(In reply to Michael Osipov from comment #12)
> I am not convinced by that approach.
Which approach? RealmBase? Context.addRoleMapping?
> I have provided a possible idea which decoupled from the
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #12 from Michael Osipov ---
(In reply to Christopher Schultz from comment #11)
> Given Context.addRoleMapping, it looks like MappingRealm just becomes a
> place for role mappings to be collected and set on the Context when the
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
Christopher Schultz changed:
What|Removed |Added
Keywords||PatchAvailable
--- Comment #11
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
Michael Osipov changed:
What|Removed |Added
Summary|Add a solution to map an|Add a solution to map a
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
https://bz.apache.org/bugzilla/show_bug.cgi?id=55477
Michael Osipov changed:
What|Removed |Added
CC||micha...@apache.org
Depends
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
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
Stefan Mayr ste...@mayr-stefan.de changed:
What|Removed |Added
Attachment #30759|0 |1
is
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #7 from Stefan Mayr ste...@mayr-stefan.de ---
Created attachment 30788
-- https://issues.apache.org/bugzilla/attachment.cgi?id=30788action=edit
Edition with inline configuration for the role mapping
I added the possibility to
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #8 from Stefan Mayr ste...@mayr-stefan.de ---
Christopers version would be like this:
Realm class=...MappingRealm
separator=,\s*
assignment=-
roleMappings=securityGroupName-innerRealmGroupName, otherName-3rdName
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #5 from Christopher Schultz ch...@christopherschultz.net ---
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.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #6 from Stefan Mayr ste...@mayr-stefan.de ---
I thought about defining a custom ressource to make an inline configuration
possible without messing with the Digester rules. So I searched and found
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #3 from Christopher Schultz ch...@christopherschultz.net ---
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).
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #4 from Stefan Mayr ste...@mayr-stefan.de ---
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:
property name=map
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #1 from Christopher Schultz ch...@christopherschultz.net ---
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:
Realm class=...MappingRealm
https://issues.apache.org/bugzilla/show_bug.cgi?id=55477
--- Comment #2 from Stefan Mayr ste...@mayr-stefan.de ---
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
26 matches
Mail list logo
