December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2076) Wrong options for auto-completion in realms of Elytron security-domain in CLI

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2076?page=com.atlassian.jira.plugi... ] Jan Kalina reassigned WFCORE-2076: ---------------------------------- Assignee: Brian Stansberry (was: Jan Kalina) > Wrong options for auto-completion in realms of Elytron security-domain in CLI > ----------------------------------------------------------------------------- > > Key: WFCORE-2076 > URL: https://issues.jboss.org/browse/WFCORE-2076 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Server > Affects Versions: 3.0.0.Alpha12 > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Labels: user_experience > > Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2076) Wrong options for auto-completion in realms of Elytron security-domain in CLI

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2076?page=com.atlassian.jira.plugi... ] Jan Kalina moved WFLY-7586 to WFCORE-2076: ------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2076 (was: WFLY-7586) Component/s: Domain Management Server (was: Security) Affects Version/s: 3.0.0.Alpha12 (was: 11.0.0.Alpha1) > Wrong options for auto-completion in realms of Elytron security-domain in CLI > ----------------------------------------------------------------------------- > > Key: WFCORE-2076 > URL: https://issues.jboss.org/browse/WFCORE-2076 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Server > Affects Versions: 3.0.0.Alpha12 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Labels: user_experience > > Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7586) Wrong options for auto-completion in realms of Elytron security-domain in CLI

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7586?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7586: ---------------------------------- Reproducible with upstream wildfly-core + elytron-subsystem (rest of wildfly or incubator versions of wildfly-core not needed). Wrong output is sent as response to "suggest-capabilities" request - not CLI problem. Problem is in CapabilityRegistry (wildfly-core/server) - getDynamicCapabilityNames(): * method is asked for security-realm capability (referencedCapability = "org.wildfly.security.security-realm") * method filter two capabilities: "org.wildfly.security.security-realm.ldapName" and "org.wildfly.security.modifiable-security-realm.ldapName" * method substring by length of referencedCapability (which cause "rity-realm.ldapName") *The problem is, that CapabilityRegistry.getDynamicCapabilityNames() obtains all paths referring some realms and create matchers from them - later all matching capabilities are obtained - even through they are not referencedCapability - must be fixed in core.* > Wrong options for auto-completion in realms of Elytron security-domain in CLI > ----------------------------------------------------------------------------- > > Key: WFLY-7586 > URL: https://issues.jboss.org/browse/WFLY-7586 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Labels: user_experience > > Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7682) PropertiesSecurityRealm error handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7682?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7682: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > PropertiesSecurityRealm error handling > -------------------------------------- > > Key: WFLY-7682 > URL: https://issues.jboss.org/browse/WFLY-7682 > Project: WildFly > Issue Type: Bug > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 11.0.0.Alpha1 > > > Following exception is not enclosed into Realm exception when problem with properties file occure: > {code:java} > org.wildfly.security.util.DecodeException: ELY03007: Invalid hex character > org.wildfly.security.util.NumericIterator$5.calc(NumericIterator.java:1074) > org.wildfly.security.util.NumericIterator$5.hasNext(NumericIterator.java:1090) > org.wildfly.security.util.ByteIterator.drainTo(ByteIterator.java:1153) > org.wildfly.security.util.ByteIterator.drain(ByteIterator.java:1165) > org.wildfly.security.auth.realm.LegacyPropertiesSecurityRealm$1.verifyEvidence(LegacyPropertiesSecurityRealm.java:171) > org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1680) > org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:655) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2075) Upgrade to WildFly Elytron 1.1.0.Beta17

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2075: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta17 Key: WFCORE-2075 URL: https://issues.jboss.org/browse/WFCORE-2075 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha14 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7716) Add tests for XA DataSource statistics

by Daniel Simko (JIRA)

[ https://issues.jboss.org/browse/WFLY-7716?page=com.atlassian.jira.plugin.... ] Daniel Simko updated WFLY-7716: ------------------------------- Description: Add new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount). (was: Added new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount).) > Add tests for XA DataSource statistics > -------------------------------------- > > Key: WFLY-7716 > URL: https://issues.jboss.org/browse/WFLY-7716 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Daniel Simko > Assignee: Daniel Simko > Priority: Minor > > Add new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7716) Add tests for XA DataSource statistics

by Daniel Simko (JIRA)

[ https://issues.jboss.org/browse/WFLY-7716?page=com.atlassian.jira.plugin.... ] Daniel Simko updated WFLY-7716: ------------------------------- Summary: Add tests for XA DataSource statistics (was: Added tests for XA DataSource statistics) > Add tests for XA DataSource statistics > -------------------------------------- > > Key: WFLY-7716 > URL: https://issues.jboss.org/browse/WFLY-7716 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Daniel Simko > Assignee: Daniel Simko > Priority: Minor > > Added new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7716) Added tests for XA DataSource statistics

by Daniel Simko (JIRA)

Daniel Simko created WFLY-7716: ---------------------------------- Summary: Added tests for XA DataSource statistics Key: WFLY-7716 URL: https://issues.jboss.org/browse/WFLY-7716 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Daniel Simko Assignee: Daniel Simko Priority: Minor Added new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-805) Allow URI for configuration for AuthenticationContext to be specified.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-805: ------------------------------------ Summary: Allow URI for configuration for AuthenticationContext to be specified. Key: ELY-805 URL: https://issues.jboss.org/browse/ELY-805 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta17 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6816) messaging-artemismq xsd is missing the initial-connect-attempts attribute

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-6816?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-6816: -------------------------------------- [~brian.stansberry] I found that new attribute was added but messaging-activemq schema was not updated. Shouldn't it be updated to 1.1 as well? > messaging-artemismq xsd is missing the initial-connect-attempts attribute > ------------------------------------------------------------------------- > > Key: WFLY-6816 > URL: https://issues.jboss.org/browse/WFLY-6816 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 10.1.0.CR1, 10.1.0.Final > > > The cluster-connection element is missing the initial-connect-attempts attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016