[JBoss JIRA] (WFCORE-3120) Tests broken as part of WildFly Core 3.0.0.Beta16
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3120?page=com.atlassian.jira.plugi... ]
Ken Wills updated WFCORE-3120:
------------------------------
Description:
Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated.
org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
was:
Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated.
org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule
org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule
org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy...
> Tests broken as part of WildFly Core 3.0.0.Beta16
> -------------------------------------------------
>
> Key: WFCORE-3120
> URL: https://issues.jboss.org/browse/WFCORE-3120
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ken Wills
> Assignee: Farah Juma
>
> Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated.
> org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
> org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9145) Tests broken as part of WildFly Core 3.0.0.Beta16
by Ken Wills (JIRA)
Ken Wills created WFLY-9145:
-------------------------------
Summary: Tests broken as part of WildFly Core 3.0.0.Beta16
Key: WFLY-9145
URL: https://issues.jboss.org/browse/WFLY-9145
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ken Wills
Assignee: Farah Juma
Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated.
org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule
org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule
org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3120) Tests broken as part of WildFly Core 3.0.0.Beta16
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3120?page=com.atlassian.jira.plugi... ]
Ken Wills moved WFLY-9145 to WFCORE-3120:
-----------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-3120 (was: WFLY-9145)
Component/s: Security
(was: Security)
> Tests broken as part of WildFly Core 3.0.0.Beta16
> -------------------------------------------------
>
> Key: WFCORE-3120
> URL: https://issues.jboss.org/browse/WFCORE-3120
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ken Wills
> Assignee: Farah Juma
>
> Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated.
> org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
> org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule
> org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule
> org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
> Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9131) Wildfly 10.1.0 Fails to load JSF message bundle from Java class
by Bobby Bassman (JIRA)
[ https://issues.jboss.org/browse/WFLY-9131?page=com.atlassian.jira.plugin.... ]
Bobby Bassman commented on WFLY-9131:
-------------------------------------
Sorry, I just noticed that I had 'Security Issue' checked. This issue is not security relevant and I change the issue to reflect that fact.
> Wildfly 10.1.0 Fails to load JSF message bundle from Java class
> ---------------------------------------------------------------
>
> Key: WFLY-9131
> URL: https://issues.jboss.org/browse/WFLY-9131
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.1.0.Final
> Environment: Windows 10
> Wildfly 10.1.0
> Reporter: Bobby Bassman
> Assignee: Farah Juma
>
> Have a war application which deploys and runs correctly on EAP 6.4. When deploying on WIldfly 10.1.0, none of the message bundle lookups work, resulting in ???zxcv??? text on JSF pages.
> This application has the following in faces-config.xml:
> <application>
> <locale-config>
> <default-locale>en</default-locale>
> <supported-locale>en_US</supported-locale>
> <supported-locale>en</supported-locale>
> </locale-config>
> <message-bundle>com.rfdinc.efile.bp.resources.CombinedMessageResources</message-bundle>
> <resource-bundle>
> <base-name>com.rfdinc.efile.bp.resources.CombinedMessageResources</base-name>
> <var>msg</var>
> </resource-bundle>
> </application>
> Here, com.rfdinc.efile.bp.resources.CombinedMessageResources is a Java class which extends java.util.ResourceBundle and implements most of the methods of java.util.ResourceBundle.
> This technique works correctly under EAP 6.4. Under Wildfly 10.1.0, however, none of the class methods ever get called. This was verified by placing logger messages throughout com.rfdinc.efile.bp.resources.CombinedMessageResources.
> Replacing <message-bundle> and <base-name> with a 'properties' file works, but this particular Java class allows us to combine multiple property files into a single resource bundle.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9131) Wildfly 10.1.0 Fails to load JSF message bundle from Java class
by Bobby Bassman (JIRA)
[ https://issues.jboss.org/browse/WFLY-9131?page=com.atlassian.jira.plugin.... ]
Bobby Bassman updated WFLY-9131:
--------------------------------
Security: (was: Security Issue)
Security Sensitive Issue: (was: This issue is security relevant)
> Wildfly 10.1.0 Fails to load JSF message bundle from Java class
> ---------------------------------------------------------------
>
> Key: WFLY-9131
> URL: https://issues.jboss.org/browse/WFLY-9131
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.1.0.Final
> Environment: Windows 10
> Wildfly 10.1.0
> Reporter: Bobby Bassman
> Assignee: Farah Juma
>
> Have a war application which deploys and runs correctly on EAP 6.4. When deploying on WIldfly 10.1.0, none of the message bundle lookups work, resulting in ???zxcv??? text on JSF pages.
> This application has the following in faces-config.xml:
> <application>
> <locale-config>
> <default-locale>en</default-locale>
> <supported-locale>en_US</supported-locale>
> <supported-locale>en</supported-locale>
> </locale-config>
> <message-bundle>com.rfdinc.efile.bp.resources.CombinedMessageResources</message-bundle>
> <resource-bundle>
> <base-name>com.rfdinc.efile.bp.resources.CombinedMessageResources</base-name>
> <var>msg</var>
> </resource-bundle>
> </application>
> Here, com.rfdinc.efile.bp.resources.CombinedMessageResources is a Java class which extends java.util.ResourceBundle and implements most of the methods of java.util.ResourceBundle.
> This technique works correctly under EAP 6.4. Under Wildfly 10.1.0, however, none of the class methods ever get called. This was verified by placing logger messages throughout com.rfdinc.efile.bp.resources.CombinedMessageResources.
> Replacing <message-bundle> and <base-name> with a 'properties' file works, but this particular Java class allows us to combine multiple property files into a single resource bundle.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9132) Applications won't deploy if their persistence.xml have multiple persistence units
by Bobby Bassman (JIRA)
[ https://issues.jboss.org/browse/WFLY-9132?page=com.atlassian.jira.plugin.... ]
Bobby Bassman commented on WFLY-9132:
-------------------------------------
Thanks Scott, adding
<property name="wildfly.jpa.default-unit" value="true" />
to persistence.xml fixed this problem.
> Applications won't deploy if their persistence.xml have multiple persistence units
> ----------------------------------------------------------------------------------
>
> Key: WFLY-9132
> URL: https://issues.jboss.org/browse/WFLY-9132
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: Windows 10 64 bit
> Wildfly 10.1.0
> Reporter: Bobby Bassman
> Assignee: Scott Marlow
>
> Applications won't deploy if their persistence.xml have multiple persistence units. This was not a problem with EAP. Now, Wildfly requires that each @PersistenceContext have a 'unitName' parameter. WIth EAP 6.4, if a @PersistenceContext did not have a 'unitName' parameter, then the default PU was used. By requiring that @PersistenceUnit have 'unitName', developers are forced to unnecessarily bind Java code to configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9134) 7.0.x ejb-security-interceptors quickstart does not work on 7.1
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-9134?page=com.atlassian.jira.plugin.... ]
Farah Juma reopened WFLY-9134:
------------------------------
Reopening since the corresponding JBEAP issue was also reopened.
> 7.0.x ejb-security-interceptors quickstart does not work on 7.1
> ---------------------------------------------------------------
>
> Key: WFLY-9134
> URL: https://issues.jboss.org/browse/WFLY-9134
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts, Security
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Blocker
> Fix For: 11.0.0.Beta1
>
>
> The quickstart should be re-added and fixed to demonstrate identity switching on EJB client with legacy security.
> As of JBoss EAP 7.1.0.ER2, this quickstart fails with the following message:
> {code}* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> Jul 10, 2017 6:24:39 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 2.1.4.Final-redhat-1
> This first round of tests is using the (PicketBox) SecurityContextAssociation API to set the desired Principal.
> -------------------------------------------------
> * * About to perform test as ConnectionUser * *
> * Making Direct Calls to the SecuredEJB
> Jul 10, 2017 6:24:39 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.6.Final-redhat-1
> Jul 10, 2017 6:24:39 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.6.Final-redhat-1
> Jul 10, 2017 6:24:39 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.18.Final-redhat-1
> Jul 10, 2017 6:24:40 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
> INFO: EJBCLIENT000017: Received server version 3 and marshalling strategies [river]
> Jul 10, 2017 6:24:40 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
> INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@57855c9a, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection(a)3b084709,channel=jboss.ejb,nodename=dev109]} on channel Channel ID d2a606da (outbound) of Remoting connection 5f282abb to localhost/127.0.0.1:8080
> * getSecurityInformation()=[Principal={ConnectionUser}, In role {User}=true, In role {RoleOne}=false, In role {RoleTwo}=false]
> * Can call roleOneMethod()=false
> * Can call roleTwoMethod()=false
> * Calling the IntermediateEJB to repeat the test server to server
> * * IntermediateEJB - Begin Testing * *
> SecuredEJBRemote.getSecurityInformation()=[Principal={ConnectionUser}, In role {User}=true, In role {RoleOne}=false, In role {RoleTwo}=false]
> Can call roleOneMethod=false
> Can call roleTwoMethod=false
> * * IntermediateEJB - End Testing * *
> * * Test Complete * *
> -------------------------------------------------
> -------------------------------------------------
> * * About to perform test as AppUserOne * *
> * Making Direct Calls to the SecuredEJB
> * * Test Complete * *
> -------------------------------------------------
> Exception in thread "main" javax.ejb.EJBAccessException: WFLYSEC0027: Invalid User
> at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:69)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:49)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:97)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor.aroundInvoke(ServerSecurityInterceptor.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.as.ejb3.component.ContainerInterceptorMethodInterceptorFactory$ContainerInterceptorMethodInterceptor.processInvocation(ContainerInterceptorMethodInterceptorFactory.java:91)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:50)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.wildfly.security.auth.server.SecurityIdentity.runAsFunctionEx(SecurityIdentity.java:380)
> at org.jboss.as.ejb3.remote.AssociationImpl.invokeWithIdentity(AssociationImpl.java:483)
> at org.jboss.as.ejb3.remote.AssociationImpl.invokeMethod(AssociationImpl.java:478)
> at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:182)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:96)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:276)
> at org.jboss.as.quickstarts.ejb_security_interceptors.ClientSecurityInterceptor.handleInvocationResult(ClientSecurityInterceptor.java:44)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocationResult(EJBObjectInterceptor.java:64)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocationResult(EJBHomeInterceptor.java:88)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:46)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:142)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:265)
> at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:453)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:204)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.getSecurityInformation(Unknown Source)
> at org.jboss.as.quickstarts.ejb_security_interceptors.RemoteClient.makeCalls(RemoteClient.java:135)
> at org.jboss.as.quickstarts.ejb_security_interceptors.RemoteClient.performTestingSecurityContext(RemoteClient.java:62)
> at org.jboss.as.quickstarts.ejb_security_interceptors.RemoteClient.main(RemoteClient.java:171){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-8418) Enhance the way licenses are presented and fix inconsistencies
by Petr Sakař (JIRA)
[ https://issues.jboss.org/browse/WFLY-8418?page=com.atlassian.jira.plugin.... ]
Petr Sakař reopened WFLY-8418:
------------------------------
> Enhance the way licenses are presented and fix inconsistencies
> --------------------------------------------------------------
>
> Key: WFLY-8418
> URL: https://issues.jboss.org/browse/WFLY-8418
> Project: WildFly
> Issue Type: Enhancement
> Components: Build System
> Reporter: Petr Sakař
> Assignee: Petr Sakař
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 11.0.0.Alpha1
>
>
> We need to provide a better view of the existing license information presented in the docs/licenses.xml file, in the form of a docs/licenses.html file that lists:
> Group/Artifact/Version/License (name+original URL)/Local Copy(relative pathname link to local copy of the license in the licenses dir).
> This can be achieved with an .xslt transformation that runs as part of the build process, which produces the desired licenses.html, and it would allow us to zip and forward the entire doc/licenses directory to a client that wants to evaluate the licenses used in Wildfly.
> In addition we need to sanitize a bit the presented licensing information:
> Licenses.html *MUST* contain a reference to the Wildfly version it applies to. It *MUST* also contain a timestamp (or build number) to uniquely identify it should it need changes within one Wildfly release cycle.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3107) Allow slave hosts to ignore missing RBAC config resources
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3107?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3107:
-------------------------------------
Fix Version/s: 4.0.0.Alpha1
> Allow slave hosts to ignore missing RBAC config resources
> ---------------------------------------------------------
>
> Key: WFCORE-3107
> URL: https://issues.jboss.org/browse/WFCORE-3107
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 4.0.0.Alpha1
>
>
> Part of parent issue whereby slaves can ignore missing RBAC constraint resources for write requests coming from the DC.
> If the DC sent the request, then the address is ok overall. So if it's missing on the slave that means the slave doesn't have that constraint registered and doesn't need to handle the op.
> This fix could possibly be backported to the 2.1.x and to EAP 6.4.x in lieu of adding transformers as part of the parent issue. In the case of 2.1.x it also allows slaves to ignore the related extension even if the code for it is present (which is only a minor benefit.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3119) Non public API leaking from Elytron subsystem
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3119?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-12406 to WFCORE-3119:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3119 (was: JBEAP-12406)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
> Non public API leaking from Elytron subsystem
> ---------------------------------------------
>
> Key: WFCORE-3119
> URL: https://issues.jboss.org/browse/WFCORE-3119
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.CR1
>
>
> The following classes are used only by the subsystem but are public: -
> org.wildfly.extension.elytron.validators.SizeValidator
> org.wildfly.extension.elytron.validators.SuffixValidator
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months