September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1640) Update AcmeClientSpi.changeAccountKey() to no longer send the newKey once the new ACME v2 changes are in production

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1640?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1640: ---------------------------------- Fix Version/s: 1.7.0.CR1 > Update AcmeClientSpi.changeAccountKey() to no longer send the newKey once the new ACME v2 changes are in production > ------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1640 > URL: https://issues.jboss.org/browse/ELY-1640 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 1.6.1.CR1, 1.7.0.CR1 > > > For ELY-1629, {{AcmeClientSpi.changeAccountKey()}} was updated to include both {{newKey}} and {{oldKey}} in the inner payload for the account key change request to prepare for the ACME v2 key rollover [breaking change|https://community.letsencrypt.org/t/acme-v2-draft-13-compliant-key...]. Currently, specifying both works fine since Let's Encrypt's staging server will expect {{oldKey}} and ignore {{newKey}} and Let's Encrypt's production server will expect {{newKey}} and ignore {{oldKey}}. However, once the new ACME v2 key rollover changes are available in Let's Encrypt's production server on Aug. 23rd, we can update this method to only include the {{oldKey}} in the inner payload. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1665) Release WildFly Elytron 1.6.1.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1665?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1665. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.6.1.Final > ----------------------------------- > > Key: ELY-1665 > URL: https://issues.jboss.org/browse/ELY-1665 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.6.1.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1664) Trace logging in SSLUtils

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1664?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1664: ---------------------------------- Fix Version/s: 1.7.0.CR1 > Trace logging in SSLUtils > ------------------------- > > Key: ELY-1664 > URL: https://issues.jboss.org/browse/ELY-1664 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.6.0.Final > Reporter: Martin Choma > Assignee: Justin Cook > Fix For: 1.6.1.CR1, 1.7.0.CR1 > > > Check Trace logging of ssl context creation. How I read code logging should apply after throw expression. That wouldn never happen. Also there is another throw of exception with SSLUtils::throwIt. > {code:java|title=org.wildfly.security.ssl.SSLUtils} > // now return a factory that will return the best match is can create. > final String[] supportedProtocols = protocolSelector.evaluate(preferredProviderByAlgorithm.keySet().toArray(NO_STRINGS)); > if (supportedProtocols.length > 0) { > return () -> { > for (String protocol : supportedProtocols) { > List<Provider> providerList = preferredProviderByAlgorithm.getOrDefault(protocol, Collections.emptyList()); > for (Provider provider : providerList) { > try { > return SSLContext.getInstance(protocol, provider); > } catch (NoSuchAlgorithmException ignored) {} > } > } > throw ElytronMessages.log.noAlgorithmForSslProtocol(); > }; > } > if (log.isTraceEnabled()) { > log.tracef("No %s provided by providers in %s: %s", SERVICE_TYPE, SSLUtils.class.getSimpleName(), Arrays.toString(providerSupplier.get())); > } > return SSLUtils::throwIt; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4114) Create the ModelTestModelControllerService variants for the supported releases

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-4114: ---------------------------------- Summary: Create the ModelTestModelControllerService variants for the supported releases Key: WFCORE-4114 URL: https://issues.jboss.org/browse/WFCORE-4114 Project: WildFly Core Issue Type: Task Components: Management Reporter: Kabir Khan Assignee: Kabir Khan These are used in the legacy-test framework -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4113) Add a commented line to standalone.conf to show how to use a custom java.security file to override all the Java security properties

by Farah Juma (JIRA)

Farah Juma created WFCORE-4113: ---------------------------------- Summary: Add a commented line to standalone.conf to show how to use a custom java.security file to override all the Java security properties Key: WFCORE-4113 URL: https://issues.jboss.org/browse/WFCORE-4113 Project: WildFly Core Issue Type: Enhancement Components: Scripts Reporter: Farah Juma Assignee: Farah Juma We should add something like this: {code} # Uncomment and edit to use a custom java.security file to override all the Java security properties #JAVA_OPTS="$JAVA_OPTS -Djava.security.properties==/path/to/custom/java.security" {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11013) Hash encoding Exception when using @DatabaseIdentityStoreDefinition

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFLY-11013?page=com.atlassian.jira.plugin... ] Martin Švehla commented on WFLY-11013: -------------------------------------- @DatabaseIdentityStoreDefinition expects password in DB to be hashed, your seems to be in plaintext. Please see here for details: https://javaee.github.io/security-api/apidocs/javax/security/enterprise/i... (TLDR is that stored password hash should be in form of <algorithm>:<iterations>:<base64(salt)>:<base64(hash)>, that's why you get error about incorrect hash encoding.) > Hash encoding Exception when using @DatabaseIdentityStoreDefinition > ------------------------------------------------------------------- > > Key: WFLY-11013 > URL: https://issues.jboss.org/browse/WFLY-11013 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 14.0.0.Final > Environment: WildFly 14. Generic Linux. JDK 8/9 > Reporter: Francesco Marchioni > Assignee: Darran Lofthouse > Attachments: javaee8-secure-servlet.zip > > > When deploying one application using @DatabaseIdentityStoreDefinition, upon successful login, the following exception is thrown > {code:java} > java.lang.IllegalArgumentException: Bad hash encoding > at org.glassfish.soteria.identitystores.hash.Pbkdf2PasswordHashImpl$EncodedPasswordHash.decode(Pbkdf2PasswordHashImpl.java:209) > at org.glassfish.soteria.identitystores.hash.Pbkdf2PasswordHashImpl$EncodedPasswordHash.<init>(Pbkdf2PasswordHashImpl.java:191) > at org.glassfish.soteria.identitystores.hash.Pbkdf2PasswordHashImpl.verify(Pbkdf2PasswordHashImpl.java:147) > at org.glassfish.soteria.identitystores.DatabaseIdentityStore.validate(DatabaseIdentityStore.java:121) > at org.glassfish.soteria.identitystores.DatabaseIdentityStore.validate(DatabaseIdentityStore.java:101) > at org.jboss.weldx.security.enterprise.identitystore.IdentityStore$635317201$Proxy$_$$_WeldClientProxy.validate(Unknown Source) > at org.glassfish.soteria.cdi.DefaultIdentityStoreHandler.validate(DefaultIdentityStoreHandler.java:97) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4112) Upgrade CLI to use aesh 1.8

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4112?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-4112: ----------------------------------------- Summary: Upgrade CLI to use aesh 1.8 (was: Upgrade to CLI to use aesh 1.8) > Upgrade CLI to use aesh 1.8 > --------------------------- > > Key: WFCORE-4112 > URL: https://issues.jboss.org/browse/WFCORE-4112 > Project: WildFly Core > Issue Type: Component Upgrade > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2818) [DMN Designer] [IE11] Rename throws an Error

by Daniel José dos Santos (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2818?page=com.atlassian.jira.plugi... ] Daniel José dos Santos reassigned DROOLS-2818: ---------------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > [DMN Designer] [IE11] Rename throws an Error > -------------------------------------------- > > Key: DROOLS-2818 > URL: https://issues.jboss.org/browse/DROOLS-2818 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Environment: IE11 > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Labels: drools-tools > > Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?* > Renaming in properties panel works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4112) Upgrade to CLI to use aesh 1.8

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-4112: -------------------------------------------- Summary: Upgrade to CLI to use aesh 1.8 Key: WFCORE-4112 URL: https://issues.jboss.org/browse/WFCORE-4112 Project: WildFly Core Issue Type: Component Upgrade Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4111) Upgrade WildFly Elytron to 1.6.1.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4111?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4111: ------------------------------------- Fix Version/s: 7.0.0.Alpha1 > Upgrade WildFly Elytron to 1.6.1.Final > -------------------------------------- > > Key: WFCORE-4111 > URL: https://issues.jboss.org/browse/WFCORE-4111 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

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 September 2018