April 2009 - jboss-identity-issues

[JBoss JIRA] Created: (JBID-64) JBoss Login Module to pick up Roles from IDM

by Anil Saldhana (JIRA)

JBoss Login Module to pick up Roles from IDM -------------------------------------------- Key: JBID-64 URL: https://jira.jboss.org/jira/browse/JBID-64 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation, IDM Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.beta1 We will need a LM that can pick up the roles of a particular user at the IDP. -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBID-63) Add JCR-based SPI Implementation.

by Jeff Yu (JIRA)

Add JCR-based SPI Implementation. --------------------------------- Key: JBID-63 URL: https://jira.jboss.org/jira/browse/JBID-63 Project: JBoss Identity Issue Type: Feature Request Components: IDM Affects Versions: 1.0.0.alpha1 Reporter: Jeff Yu Assignee: Anil Saldhana -- 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

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBID-46) Refactor the persistence.xml and database connection configuration

by Jeff Yu (JIRA)

Refactor the persistence.xml and database connection configuration ------------------------------------------------------------------ Key: JBID-46 URL: https://jira.jboss.org/jira/browse/JBID-46 Project: JBoss Identity Issue Type: Task Components: IDM Affects Versions: 1.0.0.alpha1 Reporter: Jeff Yu Assignee: Boleslaw Dawidowicz In the db scenario, I have found that we need to have the persistence.xml in the META-INF/ folder, and in the persistence.xml, we have listed a set of implementation classes. I am thinking that can we hidden those implementation classes to users somehow. such as we can have a default persistence.xml(or other name) that contains the inner implementation class in the idm-hibernate module. while for the users, they just need to configure the database connection, and we need to put the database connection properties outside. -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBID-74) org.hibernate.exception.ConstraintViolationException in updatePassword method.

by Jeff Yu (JIRA)

org.hibernate.exception.ConstraintViolationException in updatePassword method. ------------------------------------------------------------------------------ Key: JBID-74 URL: https://jira.jboss.org/jira/browse/JBID-74 Project: JBoss Identity Issue Type: Bug Components: IDM Affects Versions: 1.0.0.alpha2 Reporter: Jeff Yu Assignee: Boleslaw Dawidowicz I was trying to invoke the 'updatePassword' to update the existed password, and then it throws following exception. I've added following two lines in the 'idm-maven2-example/DBTestCase', identitySession.getAttributesManager().updatePassword(eva, "oldPassword"); identitySession.getAttributesManager().updatePassword(eva, "newPassword"); org.hibernate.exception.ConstraintViolationException: could not insert: [org.jboss.identity.idm.impl.model.hibernate.HibernateIdentityObjectCredential] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:64) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2186) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2666) at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:71) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:321) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:204) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:130) at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:154) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:110) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:61) at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:645) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:619) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:623) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:342) at $Proxy30.persist(Unknown Source) at org.jboss.identity.idm.impl.store.hibernate.HibernateIdentityStoreImpl.updateCredential(HibernateIdentityStoreImpl.java:1731) at org.jboss.identity.idm.impl.repository.WrapperIdentityStoreRepository.updateCredential(WrapperIdentityStoreRepository.java:263) at org.jboss.identity.idm.impl.api.session.managers.AttributesManagerImpl.updatePassword(AttributesManagerImpl.java:316) at org.jboss.identity.idm.example.DBTestCase.testJBossIdentity(DBTestCase.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_CT_60 in statement [insert into identity_obj_credential (id, BINARY, IDENTITY_ID, TEXT, IDENTITY_TYPE) values (null, ?, ?, ?, ?)] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:57) ... 41 more -- 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

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBID-42) SAML2: Metadata Profile

by Anil Saldhana (JIRA)

SAML2: Metadata Profile ----------------------- Key: JBID-42 URL: https://jira.jboss.org/jira/browse/JBID-42 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.alpha2 -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBID-92) LDAP based metadata provider

by Anil Saldhana (JIRA)

LDAP based metadata provider ---------------------------- Key: JBID-92 URL: https://jira.jboss.org/jira/browse/JBID-92 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.GA -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBID-90) Circle of trust configuration store

by Anil Saldhana (JIRA)

Circle of trust configuration store ----------------------------------- Key: JBID-90 URL: https://jira.jboss.org/jira/browse/JBID-90 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Affects Versions: 1.0.0.alpha2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.alpha3 Ability to store the circle of trust configuration in various data sinks such as files, DB, LDAP etc. -- 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

15 years

1
1
0 / 0

[JBoss JIRA] Created: (JBID-89) SAML2 Metadata Providers

by Anil Saldhana (JIRA)

SAML2 Metadata Providers ------------------------ Key: JBID-89 URL: https://jira.jboss.org/jira/browse/JBID-89 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Affects Versions: 1.0.0.alpha2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.alpha3 There needs to be extendable metadata providers. As a start, we can use the File based metadata providers. -- 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

15 years

1
1
0 / 0

[JBoss JIRA] Created: (JBID-78) Add methods for keystore handling to STSConfiguration

by Stefan Guilhen (JIRA)

Add methods for keystore handling to STSConfiguration ----------------------------------------------------- Key: JBID-78 URL: https://jira.jboss.org/jira/browse/JBID-78 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: 1.0.0.alpha2 Reporter: Stefan Guilhen Assignee: Anil Saldhana Fix For: 1.0.0.alpha3 In order to encrypt security tokens, the STS request handler needs to obtain the PKC of the service provider. For this reason, a method to obtain a PKC given the provider name must be added to STSConfiguration. -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBID-77) Add tests for all STS core classes

by Stefan Guilhen (JIRA)

Add tests for all STS core classes ---------------------------------- Key: JBID-77 URL: https://jira.jboss.org/jira/browse/JBID-77 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 JBoss STS implementation relies on a number of classes and factories to process a security token request. We need tests for both the STS and the helper classes to guarantee that the core engine is working as expected. -- 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

15 years

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues April 2009