4:58 a.m.
Allow a @SecurityDomain with only unauthenticatedPrincipal
----------------------------------------------------------
Key: EJBTHREE-973
URL: http://jira.jboss.com/jira/browse/EJBTHREE-973
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal
doesn't throw an IllegalStateException. Effectively the bean would run without
security, because principals can't be validated.
Note that in time the server itself will have an unauthenticatedPrincipal default which
comes from the security deployer.
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751)
--
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
4:58 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal
[ http://jira.jboss.com/jira/browse/EJBTHREE-973?page=all ]
Carlo de Wolf updated EJBTHREE-973:
-----------------------------------
Fix Version/s: EJB 3.0 RC11 - FD
Allow a @SecurityDomain with only unauthenticatedPrincipal
----------------------------------------------------------
Key: EJBTHREE-973
URL: http://jira.jboss.com/jira/browse/EJBTHREE-973
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC11 - FD
Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal
doesn't throw an IllegalStateException. Effectively the bean would run without
security, because principals can't be validated.
Note that in time the server itself will have an unauthenticatedPrincipal default which
comes from the security deployer.
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751)
--
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
4:58 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal
[ http://jira.jboss.com/jira/browse/EJBTHREE-973?page=all ]
Carlo de Wolf reassigned EJBTHREE-973:
--------------------------------------
Assignee: Carlo de Wolf
Allow a @SecurityDomain with only unauthenticatedPrincipal
----------------------------------------------------------
Key: EJBTHREE-973
URL: http://jira.jboss.com/jira/browse/EJBTHREE-973
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC11 - FD
Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal
doesn't throw an IllegalStateException. Effectively the bean would run without
security, because principals can't be validated.
Note that in time the server itself will have an unauthenticatedPrincipal default which
comes from the security deployer.
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751)
--
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
10:23 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal
[ http://jira.jboss.com/jira/browse/EJBTHREE-973?page=all ]
Anil Saldhana reassigned EJBTHREE-973:
--------------------------------------
Assignee: Anil Saldhana (was: Carlo de Wolf)
Allow a @SecurityDomain with only unauthenticatedPrincipal
----------------------------------------------------------
Key: EJBTHREE-973
URL: http://jira.jboss.com/jira/browse/EJBTHREE-973
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Assigned To: Anil Saldhana
Fix For: AS 5.0.0.Beta3
Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal
doesn't throw an IllegalStateException. Effectively the bean would run without
security, because principals can't be validated.
Note that in time the server itself will have an unauthenticatedPrincipal default which
comes from the security deployer.
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751)
--
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
10:23 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal
[ http://jira.jboss.com/jira/browse/EJBTHREE-973?page=all ]
Anil Saldhana resolved EJBTHREE-973.
------------------------------------
Resolution: Done
test-with-jvmargs:
[delete] Deleting:
C:\cygwin\home\asaldhana\jboss-5.0\jboss-head\ejb3\outputlog\test.log
[junit] Running org.jboss.ejb3.test.ejbthree973.unit.AnonymousCallerPrinciplTestCase
[junit] Found log4j.xml:
file:/C:/cygwin/home/asaldhana/jboss-5.0/jboss-hea/ejb3/src/resources/test/log4j.xml
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.843 sec
BUILD SUCCESSFUL
Total time: 13 seconds
=================================================================
If the call came with a principal, then return that. In the absence of any principal,
return the default on the security domain.
Allow a @SecurityDomain with only unauthenticatedPrincipal
----------------------------------------------------------
Key: EJBTHREE-973
URL: http://jira.jboss.com/jira/browse/EJBTHREE-973
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Assigned To: Carlo de Wolf
Fix For: AS 5.0.0.Beta3
Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal
doesn't throw an IllegalStateException. Effectively the bean would run without
security, because principals can't be validated.
Note that in time the server itself will have an unauthenticatedPrincipal default which
comes from the security deployer.
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751)
--
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
9:41 a.m.
New subject: [JBoss JIRA] Closed: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal
[ http://jira.jboss.com/jira/browse/EJBTHREE-973?page=all ]
Carlo de Wolf closed EJBTHREE-973.
----------------------------------
Allow a @SecurityDomain with only unauthenticatedPrincipal
----------------------------------------------------------
Key: EJBTHREE-973
URL: http://jira.jboss.com/jira/browse/EJBTHREE-973
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Assigned To: Anil Saldhana
Fix For: AS 5.0.0.Beta3
Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal
doesn't throw an IllegalStateException. Effectively the bean would run without
security, because principals can't be validated.
Note that in time the server itself will have an unauthenticatedPrincipal default which
comes from the security deployer.
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751)
--
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
6153
days inactive
6379
days old
5 comments
2 participants
participants (2)
-
Anil Saldhana (JIRA) -
Carlo de Wolf (JIRA)