[JBoss JIRA] (WFLY-7972) There is missing option to set absolute path for credential store.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7972:
----------------------------------
Summary: There is missing option to set absolute path for credential store.
Key: WFLY-7972
URL: https://issues.jboss.org/browse/WFLY-7972
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
There is missing option to set absolute path for credential store.
I expect absolute path defined in URI attribute. Some like this:
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/tmp/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2234) Introduce srcdeps
by Peter Palaga (JIRA)
Peter Palaga created WFCORE-2234:
------------------------------------
Summary: Introduce srcdeps
Key: WFCORE-2234
URL: https://issues.jboss.org/browse/WFCORE-2234
Project: WildFly Core
Issue Type: Task
Reporter: Peter Palaga
Assignee: Peter Palaga
Srcdeps is a tool to build Maven dependencies from their sources. With srcdeps, wildfly-core can depend on a specific commit of, e.g., undertow:
{code}
<version.io.undertow>1.4.8.Final-SRC-revision-aabbccd</version.io.undertow>
{code}
where {{aabbccd}} is the git commit id to build when any undertow artifact is requested during the build of wildfly-core.
The main advantage of srcdeps is that changes in components can be integrated and tested in wildfly-core immediately after they are committed to a public component branch. There is no need to wait for the component release.
[1] https://github.com/srcdeps/srcdeps-maven#srcdeps-maven
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7971) There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7971?page=com.atlassian.jira.plugin.... ]
Hynek Švábek updated WFLY-7971:
-------------------------------
Description:
There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
*Command with wrong filled relative-to attribute*
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource)
{code}
*You can see this log.*
Especially information about New missing/unsatisfied dependencies:is important and it wouldn't be there.
{code}
16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("credential-store" => "CredStore108")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"]
}
16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108]
{code}
*Now we try process same command without relative-to attribute*
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
{code}
*Result is success but we can notice this in log:*
{code}
16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report
WFLYCTL0185: Newly corrected services:
service jboss.server.path."non.exist.path.resource" (no longer required)
{code}
was:
There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
*Command with wrong filled relative-to attribute*
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource)
{code}
*You can see this log.*
Especially information about New missing/unsatisfied dependencies:is important and wouldn't be there.
{code}
16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("credential-store" => "CredStore108")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"]
}
16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108]
{code}
*Now we try process same command without relative-to attribute*
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
{code}
*Result is success but we can notice this in log:*
{code}
16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report
WFLYCTL0185: Newly corrected services:
service jboss.server.path."non.exist.path.resource" (no longer required)
{code}
> There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7971
> URL: https://issues.jboss.org/browse/WFLY-7971
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
>
> There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
> *Command with wrong filled relative-to attribute*
> {code}
> /subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource)
> {code}
> *You can see this log.*
> Especially information about New missing/unsatisfied dependencies:is important and it wouldn't be there.
> {code}
> 16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("credential-store" => "CredStore108")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"]
> }
> 16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108]
> {code}
> *Now we try process same command without relative-to attribute*
> {code}
> /subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
> {code}
> *Result is success but we can notice this in log:*
> {code}
> 16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report
> WFLYCTL0185: Newly corrected services:
> service jboss.server.path."non.exist.path.resource" (no longer required)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7971) There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7971:
----------------------------------
Summary: There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
Key: WFLY-7971
URL: https://issues.jboss.org/browse/WFLY-7971
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
*Command with wrong filled relative-to attribute*
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource)
{code}
*You can see this log.*
Especially information about New missing/unsatisfied dependencies:is important and wouldn't be there.
{code}
16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("credential-store" => "CredStore108")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"]
}
16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108]
{code}
*Now we try process same command without relative-to attribute*
{code}
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
{code}
*Result is success but we can notice this in log:*
{code}
16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report
WFLYCTL0185: Newly corrected services:
service jboss.server.path."non.exist.path.resource" (no longer required)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7970) Elytron keystore type default value
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7970?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-7970:
-------------------------------
Description:
Make attribute type optional during key-store creation. If not set default value "JKS" can be used.
Basically in this issue is requesting same behaviour as legacy keystore in realms
{code:jsonl|title=ManagementModel}
"keystore-provider" => {
"type" => STRING,
"description" => "The provider for loading the keystore, defaults to JKS.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "JKS",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
{code}
Extracted from WFLY-7125 and tracked as separate issue.
was:
Make attribute type optional during key-store creation. If not set default value "JKS" can be used.
Basically in this issue is requesting same behaviour as legacy keystore in realms
{code:jsonl|title=ManagementModel}
"keystore-provider" => {
"type" => STRING,
"description" => "The provider for loading the keystore, defaults to JKS.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "JKS",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
{code}
Extracted from JBEAP-6034 and tracked as separate issue.
> Elytron keystore type default value
> -----------------------------------
>
> Key: WFLY-7970
> URL: https://issues.jboss.org/browse/WFLY-7970
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
>
> Make attribute type optional during key-store creation. If not set default value "JKS" can be used.
> Basically in this issue is requesting same behaviour as legacy keystore in realms
> {code:jsonl|title=ManagementModel}
> "keystore-provider" => {
> "type" => STRING,
> "description" => "The provider for loading the keystore, defaults to JKS.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "JKS",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {code}
> Extracted from WFLY-7125 and tracked as separate issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7970) Elytron keystore type default value
by Martin Choma (JIRA)
Martin Choma created WFLY-7970:
----------------------------------
Summary: Elytron keystore type default value
Key: WFLY-7970
URL: https://issues.jboss.org/browse/WFLY-7970
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Make attribute type optional during key-store creation. If not set default value "JKS" can be used.
Basically in this issue is requesting same behaviour as legacy keystore in realms
{code:jsonl|title=ManagementModel}
"keystore-provider" => {
"type" => STRING,
"description" => "The provider for loading the keystore, defaults to JKS.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "JKS",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
{code}
Extracted from JBEAP-6034 and tracked as separate issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (ELY-896) NPE in server log if client's password is null
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/ELY-896?page=com.atlassian.jira.plugin.sy... ]
Josef Cacek commented on ELY-896:
---------------------------------
The problem was not detected by Coverity.
> NPE in server log if client's password is null
> -----------------------------------------------
>
> Key: ELY-896
> URL: https://issues.jboss.org/browse/ELY-896
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Passwords
> Reporter: Josef Cacek
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> If standalone JMS client creates connection with username and password where password is {{null}} like:
> {code}
> connectionFactory.createConnection("admin", null);
> {code}
> then server logs NPE:
> {code}
> 13:24:10,567 ERROR [org.apache.activemq.artemis.core.server] (default I/O-6) AMQ224018: Failed to create session: java.lang.NullPointerException
> at java.util.Arrays.fill(Arrays.java:2951) [rt.jar:1.8.0_71]
> at org.wildfly.security.evidence.PasswordGuessEvidence.destroy(PasswordGuessEvidence.java:53) [wildfly-elytron-1.1.0.Beta16.jar:1.1.0.Beta16]
> at org.wildfly.extension.messaging.activemq.ElytronSecurityManager.authenticate(ElytronSecurityManager.java:107)
> at org.wildfly.extension.messaging.activemq.ElytronSecurityManager.validateUser(ElytronSecurityManager.java:62)
> at org.apache.activemq.artemis.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:132)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createSession(ActiveMQServerImpl.java:1205)
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handleCreateSession(ActiveMQPacketHandler.java:156)
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handlePacket(ActiveMQPacketHandler.java:81)
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:624)
> at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:373)
> at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:356)
> at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:621)
> at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:277)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:264)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:962)
> at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435)
> at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1128)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> {code}
> Server should log the same error as if wrong password is provided:
> {code}
> 13:23:38,713 ERROR [org.apache.activemq.artemis.core.server] (default I/O-6) AMQ224018: Failed to create session: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ119031: Unable to validate user]
> at org.apache.activemq.artemis.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:144)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createSession(ActiveMQServerImpl.java:1205)
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handleCreateSession(ActiveMQPacketHandler.java:156)
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handlePacket(ActiveMQPacketHandler.java:81)
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:624)
> at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:373)
> at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:356)
> at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:621)
> at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:277)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:264)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:962)
> at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435)
> at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1128)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months