[
https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi...
]
Diana Vilkolakova commented on WFLY-14189:
------------------------------------------
This needs further investigation and if it does need to be fixed for Elytron, it might be
good to fix it by adding new configuration option in the subsystem to avoid regression for
users that might depend on the current behaviour. In that case it would be good to
implement it under WFLY-14074 . Since I will be unavailable till beginning of next year, I
will unassign myself from this issue for now.
The RunAs annotation doesn't work in EJBs with Elytron
------------------------------------------------------
Key: WFLY-14189
URL:
https://issues.redhat.com/browse/WFLY-14189
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 21.0.0.Final
Reporter: Alessandro Moscatelli
Assignee: Diana Vilkolakova
Priority: Major
Labels: ejb, elytron, regression, runas, security, startup
Fix For: 21.0.2.Final
Attachments: standalone-full-ha.new.xml, test.zip
Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain.
Everything works correctly with legacy picketbox Security Domain.
Wildfly is configured to use default "other" application-security-domain, also
using default security domain ApplicationDomain.
This exception is rised when deploying the application.
Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public
abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused
by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void
org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at
org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120)
Test/Sample project: [^test.zip]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)