[JBoss JIRA] (WFCORE-3884) Securing EJB with legacy ldap realm does not work
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3884?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-3884:
--------------------------------
Fix Version/s: (was: 5.0.0.Beta5)
> Securing EJB with legacy ldap realm does not work
> -------------------------------------------------
>
> Key: WFCORE-3884
> URL: https://issues.jboss.org/browse/WFCORE-3884
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 5.0.0.Alpha3
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 5.0.0.CR1
>
>
> Use Case: securing EJB with legacy ldap realm
> {code}
> javax.naming.NamingException: WFLYNAM0027: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.wildfly.extension.io" version 5.0.0.Final-redhat-20180517 from local module loader @2ea6137 (finder: local module finder @41ee392b (roots: /home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules,/home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.wildfly.extension.io" version 5.0.0.Final-redhat-20180517 from local module loader @2ea6137 (finder: local module finder @41ee392b (roots: /home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules,/home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules/system/layers/base))]]
> {code}
> from
> {code}
> Thread [default task-1] (Suspended)
> owns: AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer (id=500)
> UserLdapCallbackHandler.lambda$getPrincipalMapper$0(Principal) line: 143
> 2024198162.apply(Object) line: not available
> 712660640(Function<T,R>).lambda$andThen$1(Function, Object) line: 88
> 1508181426.apply(Object) line: not available
> ServerAuthenticationContext.rewriteAll(Principal, Function<Principal,Principal>, Function<Principal,Principal>, Function<Principal,Principal>) line: 1114
> ServerAuthenticationContext.assignName(SecurityIdentity, MechanismConfiguration, MechanismRealmConfiguration, Principal, Evidence, IdentityCredentials, IdentityCredentials, boolean) line: 1144
> ServerAuthenticationContext$InitialState(ServerAuthenticationContext$UnassignedState).setPrincipal(Principal, boolean) line: 1691
> ServerAuthenticationContext.setAuthenticationPrincipal(Principal, boolean) line: 408
> ServerAuthenticationContext.setAuthenticationName(String, boolean) line: 382
> ServerAuthenticationContext.setAuthenticationName(String) line: 366
> ServerAuthenticationContext$1.handleOne(Callback[], int) line: 898
> ServerAuthenticationContext$1.handle(Callback[]) line: 839
> TrustManagerSaslServerFactory.lambda$createSaslServer$0(CallbackHandler, Callback[]) line: 96
> 1848118324.handle(Callback[]) line: not available
> PlainSaslServer.evaluateResponse(byte[]) line: 117
> AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(byte[]) line: 58
> AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(byte[]) line: 106
> SecurityIdentitySaslServerFactory$1.evaluateResponse(byte[]) line: 59
> SaslUtils.evaluateResponse(SaslServer, ByteBuffer) line: 245
> SaslUtils.evaluateResponse(SaslServer, ByteBuffer, ByteBuffer) line: 217
> ServerConnectionOpenListener$AuthStepRunnable.run() line: 486
> EndpointImpl$TrackingExecutor.lambda$execute$0(Runnable) line: 926
> 1160617561.run() line: not available
> ContextClassLoaderSavingRunnable.run() line: 35
> EnhancedQueueExecutor.safeRun(Runnable) line: 1985
> EnhancedQueueExecutor$ThreadBody.doRunTask(Runnable) line: 1487
> EnhancedQueueExecutor$ThreadBody.run() line: 1349
> Thread.run() line: 748
> {code}
> Please also log somewhere this exception. It was very hard to find out.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3884) Securing EJB with legacy ldap realm does not work
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3884?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-3884:
--------------------------------
Fix Version/s: 5.0.0.CR1
> Securing EJB with legacy ldap realm does not work
> -------------------------------------------------
>
> Key: WFCORE-3884
> URL: https://issues.jboss.org/browse/WFCORE-3884
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 5.0.0.Alpha3
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 5.0.0.CR1
>
>
> Use Case: securing EJB with legacy ldap realm
> {code}
> javax.naming.NamingException: WFLYNAM0027: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.wildfly.extension.io" version 5.0.0.Final-redhat-20180517 from local module loader @2ea6137 (finder: local module finder @41ee392b (roots: /home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules,/home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.wildfly.extension.io" version 5.0.0.Final-redhat-20180517 from local module loader @2ea6137 (finder: local module finder @41ee392b (roots: /home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules,/home/mchoma/Repos/tests-ldap-kerberos/tests/target/dist/jboss-eap/modules/system/layers/base))]]
> {code}
> from
> {code}
> Thread [default task-1] (Suspended)
> owns: AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer (id=500)
> UserLdapCallbackHandler.lambda$getPrincipalMapper$0(Principal) line: 143
> 2024198162.apply(Object) line: not available
> 712660640(Function<T,R>).lambda$andThen$1(Function, Object) line: 88
> 1508181426.apply(Object) line: not available
> ServerAuthenticationContext.rewriteAll(Principal, Function<Principal,Principal>, Function<Principal,Principal>, Function<Principal,Principal>) line: 1114
> ServerAuthenticationContext.assignName(SecurityIdentity, MechanismConfiguration, MechanismRealmConfiguration, Principal, Evidence, IdentityCredentials, IdentityCredentials, boolean) line: 1144
> ServerAuthenticationContext$InitialState(ServerAuthenticationContext$UnassignedState).setPrincipal(Principal, boolean) line: 1691
> ServerAuthenticationContext.setAuthenticationPrincipal(Principal, boolean) line: 408
> ServerAuthenticationContext.setAuthenticationName(String, boolean) line: 382
> ServerAuthenticationContext.setAuthenticationName(String) line: 366
> ServerAuthenticationContext$1.handleOne(Callback[], int) line: 898
> ServerAuthenticationContext$1.handle(Callback[]) line: 839
> TrustManagerSaslServerFactory.lambda$createSaslServer$0(CallbackHandler, Callback[]) line: 96
> 1848118324.handle(Callback[]) line: not available
> PlainSaslServer.evaluateResponse(byte[]) line: 117
> AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(byte[]) line: 58
> AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(byte[]) line: 106
> SecurityIdentitySaslServerFactory$1.evaluateResponse(byte[]) line: 59
> SaslUtils.evaluateResponse(SaslServer, ByteBuffer) line: 245
> SaslUtils.evaluateResponse(SaslServer, ByteBuffer, ByteBuffer) line: 217
> ServerConnectionOpenListener$AuthStepRunnable.run() line: 486
> EndpointImpl$TrackingExecutor.lambda$execute$0(Runnable) line: 926
> 1160617561.run() line: not available
> ContextClassLoaderSavingRunnable.run() line: 35
> EnhancedQueueExecutor.safeRun(Runnable) line: 1985
> EnhancedQueueExecutor$ThreadBody.doRunTask(Runnable) line: 1487
> EnhancedQueueExecutor$ThreadBody.run() line: 1349
> Thread.run() line: 748
> {code}
> Please also log somewhere this exception. It was very hard to find out.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3748) Copying lot of commands into CLI prompt fails
by Guido Jäkel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3748?page=com.atlassian.jira.plugi... ]
Guido Jäkel edited comment on WFCORE-3748 at 5/25/18 7:10 AM:
--------------------------------------------------------------
I use "bash here documents" to pass dynamic commands to the CLI. Switching from WF-10 to WF-12, this fails while direct passing stdin with an Out-Of-Bounds-Exception at 1kB text. But if i use {{--file=/dev/stdin}} to pass the stream, i may work around the issue.
was (Author: gjaekel):
I use "bash here documents" to pass dynamic commands to the CLI. Switching from WF-10 to WF-12, this fails while direct passing stdin with an Out-Of-Bounds-Exception at 1kB text. But if i use {{ --file=/dev/stdin}} to pass the stream, i may work around the issue.
> Copying lot of commands into CLI prompt fails
> ---------------------------------------------
>
> Key: WFCORE-3748
> URL: https://issues.jboss.org/browse/WFCORE-3748
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 5.0.0.Alpha3
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
>
> Running commands with --file option works OK. Copying commands one by one works OK
> Seems to me as something is beeing overflowed.
> {code}
> [standalone@localhost:9990 /] # prepare server and client key materials
> [standalone@localhost:9990 /] # generate server keystore
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:add(type=PKCS12, credential-reference={clear-text=secret},path=/tmp/server.keystore)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:generate-key-pair(alias=server, distinguished-name="CN=server")
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:export-certificate(alias=server,path=/tmp/server.certificate.pem,pem=true)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] # generate client keystore
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:add(type=PKCS12, credential-reference={clear-text=secret},path=/tmp/client.keystore)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:generate-key-pair(alias=client, distinguished-name="CN=client")
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:export-certificate(alias=clieytron/key-store=client_truststore:import-certificate(alias=server,path=/tmp/server.certificate.pem,validate=false
> Closing ')' is missing.
> [standalone@localhost:9990 /] # save it all
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:store()
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:store()
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_truststore:store()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"elytron\"),
> (\"key-store\" => \"server_truststore\")
> ]' not found",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_truststore:store()
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3748) Copying lot of commands into CLI prompt fails
by Guido Jäkel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3748?page=com.atlassian.jira.plugi... ]
Guido Jäkel commented on WFCORE-3748:
-------------------------------------
I use "bash here documents" to pass dynamic commands to the CLI. Switching from WF-10 to WF-12, this fails while direct passing stdin with an Out-Of-Bounds-Exception at 1kB text. But if i use {{ --file=/dev/stdin}} to pass the stream, i may work around the issue.
> Copying lot of commands into CLI prompt fails
> ---------------------------------------------
>
> Key: WFCORE-3748
> URL: https://issues.jboss.org/browse/WFCORE-3748
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 5.0.0.Alpha3
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
>
> Running commands with --file option works OK. Copying commands one by one works OK
> Seems to me as something is beeing overflowed.
> {code}
> [standalone@localhost:9990 /] # prepare server and client key materials
> [standalone@localhost:9990 /] # generate server keystore
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:add(type=PKCS12, credential-reference={clear-text=secret},path=/tmp/server.keystore)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:generate-key-pair(alias=server, distinguished-name="CN=server")
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:export-certificate(alias=server,path=/tmp/server.certificate.pem,pem=true)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] # generate client keystore
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:add(type=PKCS12, credential-reference={clear-text=secret},path=/tmp/client.keystore)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:generate-key-pair(alias=client, distinguished-name="CN=client")
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:export-certificate(alias=clieytron/key-store=client_truststore:import-certificate(alias=server,path=/tmp/server.certificate.pem,validate=false
> Closing ')' is missing.
> [standalone@localhost:9990 /] # save it all
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:store()
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:store()
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_truststore:store()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"elytron\"),
> (\"key-store\" => \"server_truststore\")
> ]' not found",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_truststore:store()
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9622) Eliminate uses of ModelNode.resolve()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9622?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9622:
--------------------------------------
Clustering part of this is PR https://github.com/wildfly/wildfly/pull/11280 and branch for WFLY-10439 fixes the mod_cluster part.
> Eliminate uses of ModelNode.resolve()
> -------------------------------------
>
> Key: WFLY-9622
> URL: https://issues.jboss.org/browse/WFLY-9622
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JCA, JMS, JPA / Hibernate, Management, mod_cluster
> Reporter: Brian Stansberry
>
> Code inspection shows there are 16 uses of ModelNode.resolve() in WildFly's own code base, 12 in production code and 4 in test code. We should eliminate these, as WildFly's expression resolution is more complex than the ModelNode.resolve() contract, including vault support for which its' hard to imagine us wanting support in DMR itself. So these uses should switch to resolution from the OperationContext or, if that's not feasible, e.g. in test code, use something like ExpressionResolver.TEST_RESOLVER.
> Current uses:
> {code}
> Method
> resolve()
> Found usages (16 usages found)
> Production (12 usages found)
> Unclassified usage (12 usages found)
> wildfly-connector (3 usages found)
> org.jboss.as.connector.subsystems.common.pool (2 usages found)
> PoolConfigurationRWHandler.PoolConfigurationWriteHandler (1 usage found)
> revertUpdateToRuntime(OperationContext, ModelNode, String, ModelNode, ModelNode, List<PoolConfiguration>) (1 usage found)
> 126 updatePoolConfigs(handback, parameterName, valueToRestore.resolve());
> PoolStatisticsRuntimeAttributeWriteHandler (1 usage found)
> execute(OperationContext, ModelNode) (1 usage found)
> 58 final ModelNode resolvedValue = newValue.resolve();
> org.jboss.as.connector.subsystems.datasources (1 usage found)
> Constants (1 usage found)
> 297 validateParameter(parameterName, value.resolve());
> wildfly-jpa (4 usages found)
> org.jboss.as.jpa.management (1 usage found)
> ManagementResourceDefinition (1 usage found)
> registerAttributes(ManagementResourceRegistration) (1 usage found)
> 154 final ModelNode value = operation.get(ModelDescriptionConstants.VALUE).resolve();
> org.jboss.as.jpa.subsystem (3 usages found)
> JPASubSystemAdd (3 usages found)
> performBoottime(OperationContext, ModelNode, ModelNode) (3 usages found)
> 78 runtimeValidator.validate(operation.resolve());
> 125 final String dataSourceName = defaultDSNode.resolve().asString();
> 131 ExtendedPersistenceInheritance.valueOf(defaultExtendedPersistenceInheritanceNode.resolve().asString());
> wildfly-messaging-activemq (4 usages found)
> org.wildfly.extension.messaging.activemq.deployment (4 usages found)
> MessagingXmlInstallDeploymentUnitProcessor (4 usages found)
> deploy(DeploymentPhaseContext) (4 usages found)
> 76 final ModelNode entries = topic.getDestination().resolve().get(CommonAttributes.DESTINATION_ENTRIES.getName());
> 97 final ModelNode entries = destination.resolve().get(CommonAttributes.DESTINATION_ENTRIES.getName());
> 100 final String selector = destination.hasDefined(SELECTOR.getName()) ? destination.get(SELECTOR.getName()).resolve().asString() : null;
> 101 final boolean durable = destination.hasDefined(DURABLE.getName()) ? destination.get(DURABLE.getName()).resolve().asBoolean() : false;
> wildfly-mod_cluster-extension (1 usage found)
> org.wildfly.extension.mod_cluster (1 usage found)
> ProxyListValidator (1 usage found)
> validateResolvedParameter(String, ModelNode) (1 usage found)
> 59 validateParameter(parameterName, value.resolve());
> Test (4 usages found)
> Unclassified usage (4 usages found)
> wildfly-clustering-jgroups-extension (4 usages found)
> org.jboss.as.clustering.jgroups.subsystem (4 usages found)
> OperationsTestCase (4 usages found)
> testSubsystemReadWriteOperations() (1 usage found)
> 52 Assert.assertEquals("ee", result.get(RESULT).resolve().asString());
> testTransportReadWriteOperation() (1 usage found)
> 75 Assert.assertEquals("rack1", result.get(RESULT).resolve().asString());
> testTransportPropertyReadWriteOperation() (1 usage found)
> 114 Assert.assertEquals("true", result.get(RESULT).resolve().asString());
> testProtocolPropertyReadWriteOperation() (1 usage found)
> 195 Assert.assertEquals("value", result.get(RESULT).resolve().asString());
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10451) Configure the product release version using the galleon maven plugin
by Yeray Borges (JIRA)
Yeray Borges created WFLY-10451:
-----------------------------------
Summary: Configure the product release version using the galleon maven plugin
Key: WFLY-10451
URL: https://issues.jboss.org/browse/WFLY-10451
Project: WildFly
Issue Type: Task
Reporter: Yeray Borges
Assignee: Yeray Borges
Wildfly galleon plugin creates some manifest files including the Product Release Name and Product Release Version. Since [WFGP-18|https://issues.jboss.org/browse/WFGP-18] was merged in wildfly, we are now able to configure in the plugin not only the product name, but also the version.
This issue will configure the Product Release Version via plugin configuration. It will allow setting a different value instead of the current one which is retrieved from the maven $project.version variable.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month