[
http://jira.jboss.com/jira/browse/JBSEAM-729?page=comments#action_12363355 ]
Simon Gunzenreiner commented on JBSEAM-729:
-------------------------------------------
If the problem is getting the caller Principal without having access to Java EE APIs,
maybe this sample code, which uses a JACC mechanism, would help?
Object obj =
PolicyContext.getContext("javax.security.auth.Subject.container");
Subject subject = (Subject) obj;
if (subject != null) {
Set set = subject.getPrincipals();
// get the first principal of the Subject (assume we have only one)
for (Iterator iter = set.iterator(); iter.hasNext();) {
Principal principal = (Principal) iter.next();
return principal;
}
}
support container authorization in JBoss
----------------------------------------
Key: JBSEAM-729
URL:
http://jira.jboss.com/jira/browse/JBSEAM-729
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Reporter: Gavin King
Assigned To: Shane Bryzak
Fix For: 1.3.0.BETA1
We should use the JBoss-specific Thread->Principal binding to integrate with container
authorization. Make it extensible to support other containers in future.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira