[JBoss JIRA] (WFLY-12051) Elytron: Ability to load the attributes of an identity from multiple sources
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12051?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12051:
------------------------------------
Fix Version/s: 17.0.0.Beta1
(was: 17.0.0.Alpha1)
> Elytron: Ability to load the attributes of an identity from multiple sources
> ----------------------------------------------------------------------------
>
> Key: WFLY-12051
> URL: https://issues.jboss.org/browse/WFLY-12051
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 17.0.0.Beta1
>
>
> In previous versions a {{security-domain}} was used to merge or add roles from multiple repositories. For example the roles for the users were obtained from two different ldaps and a database. All the roles were merged and the final authenticated principal belonged to all of them. The old picketbox subsystem used stacking of login modules (and password) to implement this feature. This use-case is not rare among the customers.
> This issue is avoiding migrations from the old security subsystem to elytron.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12045) Some clustering test cases do not close JNDI InitialContext between tests
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12045?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12045:
------------------------------------
Fix Version/s: 17.0.0.Beta1
(was: 17.0.0.Alpha1)
> Some clustering test cases do not close JNDI InitialContext between tests
> -------------------------------------------------------------------------
>
> Key: WFLY-12045
> URL: https://issues.jboss.org/browse/WFLY-12045
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 17.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 17.0.0.Beta1
>
>
> The test case RemoteStatelessFailoverTestCase makes use of the helper class EJBRemoteDirectory to lookup JNDI names for beans in test cases. The EJB client then uses the resulting proxies to make invocations on the beans.
> This helper class is defined statically and initialized before any of the test cases run. Consequenty, the InitialContext created by the helper class is used across multiple test cases. The effect of this is that all of the proxies used in the test case are created from the same InitialContext. Consequently, they share a RemoteEJBDiscoveryProvider instance which is a class used to maintain information about server and module deployments which the EJB client references during invocation to find a suitable target for the invocation.
> This means that any server startup or shutdown activities are passed from one test case to another. This is not wanted as crash failures or shutdowns in one test will contaminate the next test, and this is exactly what is happening in a particular failure of this test.
> If your test class only involves one test, then static usage will work, but probably not recommended.
> UPDATE: This problem is present in a few other test cases, so I have updated them.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11991) Add Hibernate ORM transformer option to transform any method parameter of type org.hibernate.engine.spi.SessionImplementor
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11991?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11991:
------------------------------------
Fix Version/s: 17.0.0.Beta1
(was: 17.0.0.Alpha1)
> Add Hibernate ORM transformer option to transform any method parameter of type org.hibernate.engine.spi.SessionImplementor
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11991
> URL: https://issues.jboss.org/browse/WFLY-11991
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Major
> Fix For: 17.0.0.Beta1
>
> Attachments: afterchange.zip, beforechange.zip
>
>
> The idea is to transform any class method parameter of type org.hibernate.engine.spi.SessionImplementor, in user application, to instead use type org.hibernate.engine.spi.SharedSessionContractImplementor.
> The test case (change) is for this enhancement is [https://github.com/simkam/wildfly/compare/hibernate_transformer].
> The test case change is adding an internalNullSafeGet method that should also be transformed to use the SharedSessionContractImplementor type but was not, which led to an application failure with code:
> {code}
> public Object nullSafeGet(ResultSet rs, String[] names, SessionImplementor session, Object owner) throws HibernateException, SQLException {
> return internalNullSafeGet(rs, names, session, owner);
> }
> private Object internalNullSafeGet(ResultSet rs, String[] names, SessionImplementor session, Object owner) throws HibernateException, SQLException {
> internalSessionImplementorUsingMethod(session);
> session.isTransactionInProgress();
> int result = rs.getInt( names[0] );
> if ( rs.wasNull() ) return null;
> return State.values()[result];
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months