[
http://jira.jboss.com/jira/browse/JBAS-4405?page=all ]
Alex Pinkin moved SECURITY-37 to JBAS-4405:
-------------------------------------------
Project: JBoss Application Server (was: JBoss Security and Identity
Management)
Key: JBAS-4405 (was: SECURITY-37)
Component/s: Security
(was: JBossSX)
Fix Version/s: JBossAS-5.0.0.Beta3
(was: 2.0.GA)
Affects Version/s: JBossAS-5.0.0.Beta2
(was: 2.0.0.BETA)
Programmatic Web Authentication (JBoss5)
----------------------------------------
Key: JBAS-4405
URL:
http://jira.jboss.com/jira/browse/JBAS-4405
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta3
This does not come directly under JBossSX. But more from JBAS integration perspective.
This is just a tracking issue for JBAS-4077 in JBoss 5.0.x
--
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