June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8909) Disabled deployments in server group enabled after WAR is updated

by Matthew Casperson (JIRA)

Matthew Casperson created WFLY-8909: --------------------------------------- Summary: Disabled deployments in server group enabled after WAR is updated Key: WFLY-8909 URL: https://issues.jboss.org/browse/WFLY-8909 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 11.0.0.Alpha1 Environment: Centos 7 OpenJDK Reporter: Matthew Casperson Assignee: Jason Greene Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1232) Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1232?page=com.atlassian.jira.plugin.s... ] David Lloyd reassigned ELY-1232: -------------------------------- Fix Version/s: 1.1.0.Beta52 Assignee: David Lloyd (was: Darran Lofthouse) Resolution: Done > Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing > --------------------------------------------------------------------------------------------------------- > > Key: ELY-1232 > URL: https://issues.jboss.org/browse/ELY-1232 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: David Lloyd > Priority: Blocker > Labels: eap7.1-rfe-failure, eap7.1-tests-blocked > Fix For: 1.1.0.Beta52 > > > I'm not able to get SCRAM PLUS SASL mechanisms (i.e. the ones with channel binding) working. It seems there is a missing piece of integration. The mechanisms are required by EAP7-530. > I don't see the wrapper SASL factories, which are responsible for handling {{ChannelBindingCallback}}, used in the application server. (e.g. the {{TLSServerEndPointChannelBindingSaslClientFactory}}). > This issue is blocking test development. > There is still a chance the problem is in my test configuration, but the documentation of this topic is still a little bit sparse. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-894) AuthenticationConfiguration#useMechanismProperties should accept Map<String, Object> or Map<String, ?>

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-894?page=com.atlassian.jira.plugin.sy... ] David Lloyd reassigned ELY-894: ------------------------------- Fix Version/s: 1.1.0.Beta52 Assignee: David Lloyd Resolution: Done > AuthenticationConfiguration#useMechanismProperties should accept Map<String, Object> or Map<String, ?> > ------------------------------------------------------------------------------------------------------ > > Key: ELY-894 > URL: https://issues.jboss.org/browse/ELY-894 > Project: WildFly Elytron > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta52 > > > Accepting Map<String, String> is too restrictive and doesn't match existing contracts. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-811) Only AlgorithmCredentials should have parameters

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-811?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-811. ----------------------------- Fix Version/s: 1.1.0.Beta18 Resolution: Done > Only AlgorithmCredentials should have parameters > ------------------------------------------------ > > Key: ELY-811 > URL: https://issues.jboss.org/browse/ELY-811 > Project: WildFly Elytron > Issue Type: Bug > Components: Credentials > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta18 > > > Only credentials which have algorithms should have parameters. If a credential needs parameters, it probably needs an algorithm. > You need an algorithm name in order to acquire an AlgorithmParameters object, which is the only thing that can encode/decode algorithm parameters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-817) Property expansion in wildfly-client.xml

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-817?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-817. ----------------------------- Resolution: Duplicate Issue > Property expansion in wildfly-client.xml > ---------------------------------------- > > Key: ELY-817 > URL: https://issues.jboss.org/browse/ELY-817 > Project: WildFly Elytron > Issue Type: Task > Components: XML > Reporter: David Lloyd > > We need to be able to support property expansion in the configuration file. This may be something that should be supported by the client configuration library as there are multiple consumers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2932) Some Elytrons tests fails on IBM JDK in WF-CORE

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2932?page=com.atlassian.jira.plugi... ] Jan Kalina moved JBEAP-11418 to WFCORE-2932: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2932 (was: JBEAP-11418) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security Test Suite (was: Security) (was: Test Suite) Affects Version/s: 3.0.0.Beta25 (was: 7.1.0.DR18) > Some Elytrons tests fails on IBM JDK in WF-CORE > ----------------------------------------------- > > Key: WFCORE-2932 > URL: https://issues.jboss.org/browse/WFCORE-2932 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Affects Versions: 3.0.0.Beta25 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > > *Description of problem:* > Some Elytrons tests fails on IBM JDK in WF-CORE: > * org.wildfly.extension.elytron.LdapTestCase#testLdapRealmModifiability > * org.wildfly.extension.elytron.LdapTestCase#testDirContextSsl > * org.wildfly.extension.elytron.LdapTestCase#testLdapRealmDirectVerification > * org.wildfly.extension.elytron.LdapTestCase#testLdapKeyStoreMinimalCli > * org.wildfly.extension.elytron.LdapTestCase#testDirContextInsecure > * org.wildfly.extension.elytron.LdapTestCase#testDirContextSslCredential > * org.wildfly.extension.elytron.LdapTestCase#testLdapRealmIterating > * org.wildfly.extension.elytron.LdapTestCase#testLdapRealm > * org.wildfly.extension.elytron.LdapTestCase#testLdapKeyStoreMaximalService > * org.wildfly.extension.elytron.LdapTestCase#testLdapKeyStoreMaximalCli > * org.wildfly.extension.elytron.LdapTestCase#testLdapKeyStoreMinimalService > * org.wildfly.extension.elytron.LdapTestCase#testLdapKeyStoreCopyRemoveAlias > * org.wildfly.extension.elytron.RealmsTestCase#testOAuth2Realm > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_AuditLogging > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_AuthenticationClient > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_TLS > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_Mappers > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_CredentialSecurityFactories > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_ProviderLoader > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_IdentityManagement > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_SecurityProperties > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_Http > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_Ldap > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_Sasl > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_JaccWithProviders > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_CredentialStores > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testParseAndMarshalModel_Domain > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testSubsystem > * org.wildfly.extension.elytron.SubsystemParsingTestCase#testSchema > * org.wildfly.extension.elytron.TlsTestCase#testSslServiceAuth > * org.wildfly.extension.elytron.TlsTestCase#testProviderTrustManager > * org.wildfly.extension.elytron.TlsTestCase#testSslServiceAuthRequiredButNotProvided > * org.wildfly.extension.elytron.TlsTestCase#testSslServiceNoAuth > This test errors was not fixed in JBEAP-9620, so I create new jira for it (see [comment from JBEAP-9620|https://issues.jboss.org/browse/JBEAP-9620?focusedCommentId=13...]) > *How reproducible:* > 100% > *Actual results:* > I attached surefire logs to this jira. > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-870) AbstractAlgorithmParametersSpiImpl::engineInit is using wrong reference

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-870?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-870. ----------------------------- Fix Version/s: 1.1.0.Beta20 Resolution: Done > AbstractAlgorithmParametersSpiImpl::engineInit is using wrong reference > ----------------------------------------------------------------------- > > Key: ELY-870 > URL: https://issues.jboss.org/browse/ELY-870 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Zoran Regvart > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 1.1.0.Beta20 > > > The {{AbstractAlgorithmParametersSpiImpl::engineInit(AlgorithmParameterSpec)}} to test the instance of the given {{AlgorithmParameterSpec}} is using the class's field instead of the given parameter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-900) CredentialSource equals and hashCode

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-900?page=com.atlassian.jira.plugin.sy... ] David Lloyd closed ELY-900. --------------------------- Resolution: Out of Date > CredentialSource equals and hashCode > ------------------------------------ > > Key: ELY-900 > URL: https://issues.jboss.org/browse/ELY-900 > Project: WildFly Elytron > Issue Type: Bug > Components: Credentials > Reporter: David Lloyd > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-959) Coverity static analysis: Serializable *Callback classes containes non-serializable fields

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-959?page=com.atlassian.jira.plugin.sy... ] David Lloyd reassigned ELY-959: ------------------------------- Assignee: David Lloyd > Coverity static analysis: Serializable *Callback classes containes non-serializable fields > ------------------------------------------------------------------------------------------ > > Key: ELY-959 > URL: https://issues.jboss.org/browse/ELY-959 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta24 > Reporter: Martin Choma > Assignee: David Lloyd > > Coverity static analysis found, there is couple of *Callback classes, which are mark as Serializable, and contains non-serializable fields. > * CredentialCallback > * CredentialUpdateCallback > * MechanismInformationCallback > * SSLCallback > * SecurityIdentityCallback > * ServerCredentialCallback > * TrustedAuthoritiesCallback > Either mark fields as transient or Serializable. > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84905... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-967) Impossible to authorize as a non-name Principal

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-967?page=com.atlassian.jira.plugin.sy... ] David Lloyd reassigned ELY-967: ------------------------------- Assignee: David Lloyd > Impossible to authorize as a non-name Principal > ----------------------------------------------- > > Key: ELY-967 > URL: https://issues.jboss.org/browse/ELY-967 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI, Authentication Server > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > > There are no methods on SecurityIdentity to create a run-as authorized user with a Principal, only a String name. There is no authorize(Principal) variant on ServerAuthenticationContext. > These should be added to support realms which do not use plain text names to identify users. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017