"scott.stark(a)jboss.org" wrote : We just need to support the introduction of static roles. Where authentication is done to obtain a Subject, a post authentication interceptor can be added to optionally associated deployment level roles + mappings. This interceptor would have to be in between the authentication and authorization interceptors.
|
| In the web container, the construction of the JBossGenericPrincipal roles needs to consult the deployment metadata.
|
That made perfect sense. Thanks Scott.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018057#4018057
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018057
We just need to support the introduction of static roles. Where authentication is done to obtain a Subject, a post authentication interceptor can be added to optionally associated deployment level roles + mappings. This interceptor would have to be in between the authentication and authorization interceptors.
In the web container, the construction of the JBossGenericPrincipal roles needs to consult the deployment metadata.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018001#4018001
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018001
Topic: Support deployment level principal-role mapping via jboss.xml.
If there is deployment level principal-role mapping done by the user, we should be able to take this into account during authorization decisions.
Here is an example of this mapping:
| <jboss>
| <assembly-descriptor>
| <security-role>
| <role-name>Administrator</role-name>
| <principal-name>j2ee</principal-name>
| </security-role>
| <security-role>
| <role-name>Employee</role-name>
| <principal-name>javajoe</principal-name>
| <principal-name>j2ee</principal-name>
| </security-role>
| </assembly-descriptor>
| </jboss>
|
This info is available in the metadata and can be obtained in the JBossSX layer.
The previous approach of "DeploymentRolesLoginModule" was unaccepted.
http://www.mail-archive.com/jboss-development@lists.sourceforge.net/msg65...
Any ideas about solving this properly?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017903#4017903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017903
First things noted:
- Is the IdentityLoginModule still used?
- Can I change the IdentityService to be a real service?
- Rename the IdentitySession to DBIdentityService and the IdentyiSessionFactory to DBIdentityServiceFactory?
browsing any further through the identity code.... does it need cleaning up? Old classes there? Older ideas? JbpmSession... methods only used in tests.... Maybe one or two classes are used to emulate/mock the real loginmodule... could someone please comment before I go further...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017881#4017881
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017881