April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2397) Elytron simple-regex-realm-mapper "pattern" attribute has wrong description.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2397?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2397: ------------------------------------- Fix Version/s: 3.0.0.Beta17 (was: 3.0.0.Beta16) > Elytron simple-regex-realm-mapper "pattern" attribute has wrong description. > ---------------------------------------------------------------------------- > > Key: WFCORE-2397 > URL: https://issues.jboss.org/browse/WFCORE-2397 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Chao Wang > Fix For: 3.0.0.Beta17 > > > Elytron simple-regex-realm-mapper "pattern" attribute has wrong description [1]. > *Actual description* > {code} > The regular expression to use for this NameRewriter. > {code} > *Expected description* > Some like that (from DMR): > {code} > The regular expression which must contain at least one capture group to extract the realm from the name. > {code} > [1] https://github.com/wildfly-security/elytron-subsystem/blob/580569d17cb6c3... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2528) Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2528?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2528: ------------------------------------- Fix Version/s: 3.0.0.Beta17 (was: 3.0.0.Beta16) > Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase > ---------------------------------------------------------------------- > > Key: WFCORE-2528 > URL: https://issues.jboss.org/browse/WFCORE-2528 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta17 > > > Leftover cleanup from WFCORE-1958 since VaultPasswordsInCLITestCase is not enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2521) TLS between domain and host controllers does not work

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2521?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2521: ------------------------------------- Fix Version/s: 3.0.0.Beta17 (was: 3.0.0.Beta16) > TLS between domain and host controllers does not work > ----------------------------------------------------- > > Key: WFCORE-2521 > URL: https://issues.jboss.org/browse/WFCORE-2521 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: domain-management, domain-mode, eap71_alpha, regression, ssl > Fix For: 3.0.0.Beta17 > > > This is regression against EAP 7.0 . Customers relying on this feature won't be able to migrate to EAP 7.1. > Working configuration of TLS between domain and host controller from EAP 7.0 (legacy) does not work on EAP 7.1 anymore. > In server log there is this error: > {code:title=server.log} > [Host Controller] Caused by: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL > [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:527) > [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:477) > [Host Controller] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > [Host Controller] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > [Host Controller] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > [Host Controller] at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) > [Host Controller] at ...asynchronous invocation...(Unknown Source) > [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:466) > [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:437) > [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:430) > [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:163) > [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119) > [Host Controller] ... 9 more > {code} > See attached server.log for context log. > Tests in wildfly-core covering this scenario are currently ignored: > * SSLMasterSlaveOneWayTestCase is ignored by WFCORE-1978 > * SSLMasterSlaveTwoWayTestCase is ignored by WFCORE-2068 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2694) Upgrade WildFly Common to 1.2.0.Beta10

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2694?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2694: ------------------------------------- Fix Version/s: 3.0.0.Beta17 (was: 3.0.0.Beta16) > Upgrade WildFly Common to 1.2.0.Beta10 > -------------------------------------- > > Key: WFCORE-2694 > URL: https://issues.jboss.org/browse/WFCORE-2694 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta17 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2664) Eliminate MSC optional dependency usage in RemotingServices

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2664?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2664: ------------------------------------- Fix Version/s: 3.0.0.Beta17 (was: 3.0.0.Beta16) > Eliminate MSC optional dependency usage in RemotingServices > ----------------------------------------------------------- > > Key: WFCORE-2664 > URL: https://issues.jboss.org/browse/WFCORE-2664 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 3.0.0.Beta14 > Reporter: Richard Opalka > Assignee: Brian Stansberry > Fix For: 3.0.0.Beta17 > > > RemotingServices.installConnectorServices() uses MSC optional dependency. > Any change this MSC optional dependency usage might be eliminated there? > Maybe OperationContext.hasOptionalCapability() could be used > in ManagementRemotingServices.installDomainConnectorServices() method? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2661) Upgrade Elytron Web to 1.0.0.Beta15

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2661?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2661: ------------------------------------- Fix Version/s: 3.0.0.Beta17 (was: 3.0.0.Beta16) > Upgrade Elytron Web to 1.0.0.Beta15 > ----------------------------------- > > Key: WFCORE-2661 > URL: https://issues.jboss.org/browse/WFCORE-2661 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta17 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JASSIST-266) Coredump occurred when monitoring lambda application with javassist implemented APM

by lu zhongda (JIRA)

lu zhongda created JASSIST-266: ---------------------------------- Summary: Coredump occurred when monitoring lambda application with javassist implemented APM Key: JASSIST-266 URL: https://issues.jboss.org/browse/JASSIST-266 Project: Javassist Issue Type: Bug Affects Versions: 3.20.0-GA Environment: JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 1.8.0_25-b17) Reporter: lu zhongda Assignee: Shigeru Chiba Priority: Critical Fix For: 3.22.0-GA JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 1.8.0_25-b17) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops) Problematic frame: j java.lang.invoke.BoundMethodHandle$Species_LL.clone(Ljava/lang/invoke/MethodType;Ljava/lang/invoke/LambdaForm;)Ljava/lang/invoke/BoundMethodHandle;+1255301938 Core dump written. Default location: /apmhome/weblogic/domains/APM_Domain/core or core.895 (max size 10485760 kB). To ensure a full core dump, try "ulimit -c unlimited" before starting Java again -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2682) Elytron token-realm attributes validations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2682?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2682: ------------------------------------------ This looks like a duplicate of WFCORE-2317; should be fixed. > Elytron token-realm attributes validations > ------------------------------------------ > > Key: WFCORE-2682 > URL: https://issues.jboss.org/browse/WFCORE-2682 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta13 > Reporter: Martin Choma > > * I am able to set both {{key-store}} and {{public-key}} attributes. However based on model they should be alternatives and thus only one of them should be allowed. > * Althought, {{key-store}} and {{certificate}} are configured as requires in model, validation does not work. > Seems it is caused by WFCORE-2317. > {code} > "public-key" => { > "type" => STRING, > "description" => "A public key in PEM Format. During validation, if a public key is provided, signature will be verified based on the key you provided here.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "alternatives" => [ > "key-store", > "certificate" > ], > "min-length" => 1L, > "max-length" => 2147483647L > }, > "key-store" => { > "type" => STRING, > "description" => "A key store from where the certificate with a public key should be loaded from.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "alternatives" => ["public-key"], > "requires" => ["certificate"], > "capability-reference" => "org.wildfly.security.key-store", > "min-length" => 1L, > "max-length" => 2147483647L > }, > "certificate" => { > "type" => STRING, > "description" => "The name of the certificate with a public key to load from the key store.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "alternatives" => ["public-key"], > "requires" => ["key-store"], > "min-length" => 1L, > "max-length" => 2147483647L > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8630) Tests broken as part of WildFly Core 3.0.0.Beta16

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8630?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8630: ---------------------------------------- WFLY-8628 looks like it's about the 2 SwitchIdentityTestCase failures. > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFLY-8630 > URL: https://issues.jboss.org/browse/WFLY-8630 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8630) Tests broken as part of WildFly Core 3.0.0.Beta16

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8630?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8630: ---------------------------------------- It's *possible* these can be corrected via a change in full tomorrow. Two of the 4 (SwitchIdentityTestCase) had edits in the ladybird PR, so maybe something needs tweaking. And the CLISecurityTestCase is checking the CLI can't authenticate, and it can't, which is good. But the output from the CLI is different than the assert. That may or may not be a meaningful issue. SlaveHostControllerElytronAuthenticationTestCase is failing in a test of using PLAIN auth. So of course we want that fixed but I don't know whether it's critical enough to delay the DR or cram in a new core release. > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFLY-8630 > URL: https://issues.jboss.org/browse/WFLY-8630 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > > 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)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017