Deploy identity platform as a sar in JBossAS 5
----------------------------------------------
Key: JBID-69
URL: https://jira.jboss.org/jira/browse/JBID-69
Project: JBoss Identity
Issue Type: Feature Request
Components: SOARequirements
Reporter: Jeff Yu
Assignee: Jeff Yu
Deploy the identity platform as a sar in JBoss AS 5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Generate the DDL script in the build process
--------------------------------------------
Key: JBID-70
URL: https://jira.jboss.org/jira/browse/JBID-70
Project: JBoss Identity
Issue Type: Feature Request
Components: IDM
Reporter: Jeff Yu
Assignee: Jeff Yu
Generate the IDM DDL script in the build process.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Using izpack to do the installation for IDM component.
------------------------------------------------------
Key: JBID-80
URL: https://jira.jboss.org/jira/browse/JBID-80
Project: JBoss Identity
Issue Type: Task
Components: IDM
Reporter: Jeff Yu
Assignee: Jeff Yu
Using izpack to do the installation for IDM component.
Like jBPM4, use izpack library to ask users to pick the container (like JBoss5), and the database (like HSQLDB, Postgrels etc), and then install it into the specific container.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Merge the STS configuration schema with the jboss-identity-fed.xsd that already exists
--------------------------------------------------------------------------------------
Key: JBID-75
URL: https://jira.jboss.org/jira/browse/JBID-75
Project: JBoss Identity
Issue Type: Task
Components: Identity-Federation
Affects Versions: 1.0.0.alpha2
Reporter: Stefan Guilhen
Assignee: Stefan Guilhen
Fix For: 1.0.0.alpha3
The Security Token Service currently uses a separate schema for its configuration. This schema, however redefines several constructs that already exist in the jboss-identity-fed.xsd for dealing with key and trust stores. Besides, there's no need for a separate schema just for the STS. By having a single schema, not only it is easier to manage all the configuration aspects but also we can reuse existing constructs for dealing with keystores.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Improve the current configuration tests to incorporate STS scenarios.
---------------------------------------------------------------------
Key: JBID-76
URL: https://jira.jboss.org/jira/browse/JBID-76
Project: JBoss Identity
Issue Type: Sub-task
Components: Identity-Federation
Affects Versions: 1.0.0.alpha2
Reporter: Stefan Guilhen
Assignee: Stefan Guilhen
Fix For: 1.0.0.alpha3
We need to add STS scenarios to ConfigUnitTestCase
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira