[
https://issues.jboss.org/browse/WFLY-8562?page=com.atlassian.jira.plugin....
]
Farah Juma updated WFLY-8562:
-----------------------------
Description: {{ClientLoginModule}} won't work when used to invoke EJBs backed by
Elytron. Add a test utility to ensure that tests use the ClientLoginModule approach for
PicketBox deployments and the Elytron approach for Elytron deployments when attempting to
switch the user's identity. All tests that currently make use of the ClientLoginModule
approach will need to be updated to make use of the new utility. This will ensure that the
tests will be able to run properly with and without the Elytron profile enabled. (was:
{{ClientLoginModule}} does not establish client caller identity and credentials when used
to invoke EJBs backed by Elytron {{application-security-domain}}.
This issue affects easy migration to Elytron as no instructions to replace this have been
provided as well as AS TS testing with Elytron profile since nearly every test case in
{{org.jboss.as.test.integration.ejb.remote.security}} uses CLM to establish
identity/credentials.)
Add a test utility to ensure that tests use the ClientLoginModule
approach for PicketBox deployments and the Elytron approach for Elytron deployments and
update all affected tests
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-8562
URL:
https://issues.jboss.org/browse/WFLY-8562
Project: WildFly
Issue Type: Bug
Components: EJB, Security, Test Suite
Reporter: Farah Juma
Assignee: Farah Juma
Priority: Blocker
Labels: eap7.1-rfe-blocker, eap71_beta
{{ClientLoginModule}} won't work when used to invoke EJBs backed by Elytron. Add a
test utility to ensure that tests use the ClientLoginModule approach for PicketBox
deployments and the Elytron approach for Elytron deployments when attempting to switch the
user's identity. All tests that currently make use of the ClientLoginModule approach
will need to be updated to make use of the new utility. This will ensure that the tests
will be able to run properly with and without the Elytron profile enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)