[JBoss JIRA] (WFLY-7536) RemotingLoginModuleUseNewClientCertTestCase fails on IBM jdk
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7536?page=com.atlassian.jira.plugin.... ]
Martin Choma reassigned WFLY-7536:
----------------------------------
Assignee: Martin Choma (was: Tomaz Cerar)
> RemotingLoginModuleUseNewClientCertTestCase fails on IBM jdk
> ------------------------------------------------------------
>
> Key: WFLY-7536
> URL: https://issues.jboss.org/browse/WFLY-7536
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 11.0.0.Alpha1
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160427_1620_B301573
> JIT - tr.r14.java.green_20160329_114288
> GC - R28_Java8_SR3_20160427_1620_B301573_CMPRSS
> J9CL - 20160427_301573)
> JCL - 20160421_01 based on Oracle jdk8u91-b14
> Reporter: Martin Choma
> Assignee: Martin Choma
>
> testAuthorizedClient and testNotAuthorizedClient tests from RemotingLoginModuleUseNewClientCertTestCase fails on IBM jdk with {{javax.net.ssl.SSLException: Received fatal alert: handshake_failure)}}
> *reproduce*
> {noformat}
> $ ./integration-tests.sh -Dts.noSmoke -Dts.basic -Dtest=RemotingLoginModuleUseNewClientCertTestCase
> {noformat}
> {noformat}
> testNotAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase) Time elapsed: 0.079 sec <<< ERROR!
> javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
> at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
> at javax.naming.InitialContext.lookup(InitialContext.java:428)
> at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase.testNotAuthorizedClient(RemotingLoginModuleUseNewClientCertTestCase.java:180)
> testAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase) Time elapsed: 0.046 sec <<< ERROR!
> javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
> at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
> at javax.naming.InitialContext.lookup(InitialContext.java:428)
> at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase.testAuthorizedClient(RemotingLoginModuleUseNewClientCertTestCase.java:166)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7536) RemotingLoginModuleUseNewClientCertTestCase fails on IBM jdk
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7536?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-7006 to WFLY-7536:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7536 (was: JBEAP-7006)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR6)
> RemotingLoginModuleUseNewClientCertTestCase fails on IBM jdk
> ------------------------------------------------------------
>
> Key: WFLY-7536
> URL: https://issues.jboss.org/browse/WFLY-7536
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 11.0.0.Alpha1
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160427_1620_B301573
> JIT - tr.r14.java.green_20160329_114288
> GC - R28_Java8_SR3_20160427_1620_B301573_CMPRSS
> J9CL - 20160427_301573)
> JCL - 20160421_01 based on Oracle jdk8u91-b14
> Reporter: Martin Choma
> Assignee: Tomaz Cerar
>
> testAuthorizedClient and testNotAuthorizedClient tests from RemotingLoginModuleUseNewClientCertTestCase fails on IBM jdk with {{javax.net.ssl.SSLException: Received fatal alert: handshake_failure)}}
> *reproduce*
> {noformat}
> $ ./integration-tests.sh -Dts.noSmoke -Dts.basic -Dtest=RemotingLoginModuleUseNewClientCertTestCase
> {noformat}
> {noformat}
> testNotAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase) Time elapsed: 0.079 sec <<< ERROR!
> javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
> at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
> at javax.naming.InitialContext.lookup(InitialContext.java:428)
> at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase.testNotAuthorizedClient(RemotingLoginModuleUseNewClientCertTestCase.java:180)
> testAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase) Time elapsed: 0.046 sec <<< ERROR!
> javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
> at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
> at javax.naming.InitialContext.lookup(InitialContext.java:428)
> at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleUseNewClientCertTestCase.testAuthorizedClient(RemotingLoginModuleUseNewClientCertTestCase.java:166)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7535) filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7535?page=com.atlassian.jira.plugin.... ]
Hynek Švábek updated WFLY-7535:
-------------------------------
Description:
Fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
*Scenario*
I want to create "identity" for Elytron filesystem-realm with constant-name-rewriter (or others *-name-rewriter(s) with same behaviour).
I am not able create more then one identity (because name is rewriten to same name).
It is right behaviour but fail-description contains confusing message with OLD resource name.
*Steps to reproduce*
* /subsystem=elytron/constant-name-rewriter=constantNR001:add(constant=constantName)
* /subsystem=elytron/filesystem-realm=fsRealm123:add(path=fs123, relative-to=jboss.server.config.dir,levels=1, name-rewriter=constantNR001)
* /subsystem=elytron/filesystem-realm=fsRealm123/identity=identity001:add()
I want add second identity with name "identity002" which is rewriten to *constantName*. I expect fail because the identity with *constantName* exists.
/subsystem=elytron/filesystem-realm=fsRealm123/identity=identity002:add()
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.",
"rolled-back" => true
}
{code}
*Suggestion for solution*
Message should contain some information about *constantName* at least. Information about nameRewriter will be also fine.
e.g. "WFLYELY01000: Identity with name [identity002] which was rewritten to [constantName] already exists. Name-rewriter was used."
was:
Fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
Scenario
I want to create "identity" for Elytron filesystem-realm with constant-name-rewriter (or others *-name-rewriter(s) with same behaviour).
I am not able create more then one identity (because name is rewriten to same name).
It is right behaviour but fail-description contains confusing message with OLD resource name.
Steps to reproduce
/subsystem=elytron/constant-name-rewriter=constantNR001:add(constant=constantName)
/subsystem=elytron/filesystem-realm=fsRealm123:add(path=fs123, relative-to=jboss.server.config.dir,levels=1, name-rewriter=constantNR001)
/subsystem=elytron/filesystem-realm=fsRealm123/identity=identity001:add()
I want add second identity with name "identity002" which is rewriten to "constantName". I expect fail because the identity with "constantName" exists.
/subsystem=elytron/filesystem-realm=fsRealm123/identity=identity002:add()
{
"outcome" => "failed",
"failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.",
"rolled-back" => true
}
Suggestion for solution
Message should contain some information about "constantName" at least. Information about nameRewriter will be also fine.
e.g. "WFLYELY01000: Identity with name [constantName] already exists. Name-rewriter was used."
> filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7535
> URL: https://issues.jboss.org/browse/WFLY-7535
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
>
> Fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
> *Scenario*
> I want to create "identity" for Elytron filesystem-realm with constant-name-rewriter (or others *-name-rewriter(s) with same behaviour).
> I am not able create more then one identity (because name is rewriten to same name).
> It is right behaviour but fail-description contains confusing message with OLD resource name.
> *Steps to reproduce*
> * /subsystem=elytron/constant-name-rewriter=constantNR001:add(constant=constantName)
> * /subsystem=elytron/filesystem-realm=fsRealm123:add(path=fs123, relative-to=jboss.server.config.dir,levels=1, name-rewriter=constantNR001)
> * /subsystem=elytron/filesystem-realm=fsRealm123/identity=identity001:add()
> I want add second identity with name "identity002" which is rewriten to *constantName*. I expect fail because the identity with *constantName* exists.
> /subsystem=elytron/filesystem-realm=fsRealm123/identity=identity002:add()
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.",
> "rolled-back" => true
> }
> {code}
> *Suggestion for solution*
> Message should contain some information about *constantName* at least. Information about nameRewriter will be also fine.
> e.g. "WFLYELY01000: Identity with name [identity002] which was rewritten to [constantName] already exists. Name-rewriter was used."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1942) Remove the $local use from the default mgmt-users.properties
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1942?page=com.atlassian.jira.plugi... ]
Darran Lofthouse resolved WFCORE-1942.
--------------------------------------
Fix Version/s: 3.0.0.Alpha12
(was: 3.0.0.Alpha13)
Resolution: Rejected
This was not added in the end as an identity-realm was added to the Elytron subsystem to contain this special user.
> Remove the $local use from the default mgmt-users.properties
> ------------------------------------------------------------
>
> Key: WFCORE-1942
> URL: https://issues.jboss.org/browse/WFCORE-1942
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 3.0.0.Alpha12
>
>
> The subsystem will be enhanced so that an identity-security-realm can be defined with some hard coded identities, once defined we can remove the $local user from the properties file(s)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7535) filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7535:
----------------------------------
Summary: filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
Key: WFLY-7535
URL: https://issues.jboss.org/browse/WFLY-7535
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
Scenario
I want to create "identity" for Elytron filesystem-realm with constant-name-rewriter (or others *-name-rewriter(s) with same behaviour).
I am not able create more then one identity (because name is rewriten to same name).
It is right behaviour but fail-description contains confusing message with OLD resource name.
Steps to reproduce
/subsystem=elytron/constant-name-rewriter=constantNR001:add(constant=constantName)
/subsystem=elytron/filesystem-realm=fsRealm123:add(path=fs123, relative-to=jboss.server.config.dir,levels=1, name-rewriter=constantNR001)
/subsystem=elytron/filesystem-realm=fsRealm123/identity=identity001:add()
I want add second identity with name "identity002" which is rewriten to "constantName". I expect fail because the identity with "constantName" exists.
/subsystem=elytron/filesystem-realm=fsRealm123/identity=identity002:add()
{
"outcome" => "failed",
"failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.",
"rolled-back" => true
}
Suggestion for solution
Message should contain some information about "constantName" at least. Information about nameRewriter will be also fine.
e.g. "WFLYELY01000: Identity with name [constantName] already exists. Name-rewriter was used."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7534) Enabling statistics on transactions subsystem shouldn't require reload of server
by Daniel Simko (JIRA)
[ https://issues.jboss.org/browse/WFLY-7534?page=com.atlassian.jira.plugin.... ]
Daniel Simko moved JBEAP-7002 to WFLY-7534:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7534 (was: JBEAP-7002)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Transactions
(was: Transactions)
(was: User Experience)
> Enabling statistics on transactions subsystem shouldn't require reload of server
> --------------------------------------------------------------------------------
>
> Key: WFLY-7534
> URL: https://issues.jboss.org/browse/WFLY-7534
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Daniel Simko
> Assignee: Tom Jenkinson
>
> /subsystem=transactions:write-attribute(name=statistics-enabled, value=true)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months