November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by Paul Carroll (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] Paul Carroll commented on ELY-1435: ----------------------------------- I have rpa5cxtF2rP7Q0eurqaIrQ== stored in my SALT_VALUE column, Y7IZ4JS8F2eK+/Ii/fDhaaWQ8hBGYjQ= stored in the PASSWORD column and 10 stored in the ITERATION_COUNT column. > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by Paul Carroll (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] Paul Carroll commented on ELY-1435: ----------------------------------- This is the hash I generate when I use the ModularCrypt method. $2a$10$Jft5e/f6tbQcFxGImy8xweU/1zD22Ca9e9AlgWu0w9zMeBGyHcvPq > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1435: ---------------------------------- You had {{$2a$10$rpa5cxtF2rP7Q0eurqaIrQ==Y7IZ4JS8F2eK+/Ii/fDhaaWQ8hBGYjQ=}} stored in you database? > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by Paul Carroll (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] Paul Carroll commented on ELY-1435: ----------------------------------- That is what I had stored in my database and the Elytron <bcrypt-mapper> authenticated it successfully. I used the program from the forum discussion to create the hash. > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1435: ---------------------------------- Since it's not 100% clear what code generated what piece, I"ll just point out here that modular crypt (i.e. the password format which starts with "$2a$...") does not use the standard base64 alphabet; it uses a special mod-crypt one. So if the above example was created similarly to the example code in the forum thread, it's never going to validate (with or without the invalid padding characters). To encode an Elytron password into its modular-crypt form, do this: {code:java} import org.wildfly.security.password.util.ModularCrypt; // ... and inside your method ... Password p = ...; String str = ModularCrypt.encodeAsString(p); {code} > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9526) Mixed domain tests are launching legacy slaves using current jboss-modules.jar

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9526?page=com.atlassian.jira.plugin.... ] Brian Stansberry closed WFLY-9526. ---------------------------------- Resolution: Rejected Wrong; totally wrong. If baseConfig is supplied, it is used, so all its state is retained. > Mixed domain tests are launching legacy slaves using current jboss-modules.jar > ------------------------------------------------------------------------------ > > Key: WFLY-9526 > URL: https://issues.jboss.org/browse/WFLY-9526 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Priority: Minor > > DomainTestSupport.Configuration.getSlaveConfiguration(String hostConfigPath, String testName, String hostName, WildFlyManagedConfiguration baseConfig, boolean readOnlyHost, boolean debug) drops any configured jboss.home from the passed in baseConfig, which results in the default one being used. That's fine for the normal testsuite/domain in wildfly core and full wildfly, as all the domain processes in those test modules use the same installation, just with different writable dirs per HC. But in mixed domain it means the legacy slaves are using jboss-modules.jar from the current version, not their own. > This is a minor bug as it seems to not cause any harm, but it could blow up somehow if something changes, and regardless it's not right to run a legacy slave that's not really running legacy software. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by Paul Carroll (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] Paul Carroll commented on ELY-1435: ----------------------------------- That would be Elytron. I generated the hash using the Wildfly API. Authentication failed for the hashes I generated with jBCrypt. > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1435: ----------------------------------- This hash ($2a$10$rpa5cxtF2rP7Q0eurqaIrQ==Y7IZ4JS8F2eK+/Ii/fDhaaWQ8hBGYjQ=) is marked as invalid by online validators [3][4][5] > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1435: ---------------------------------- None of the fields should be using trailing padding ("=" characters). Is Elytron doing that, or is JBCrypt doing that? > Elytron BCrypt Mapper Not Working with jBCrypt > ---------------------------------------------- > > Key: ELY-1435 > URL: https://issues.jboss.org/browse/ELY-1435 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Affects Versions: 1.0.0.Final > Environment: Wildfly 11.0.0.Final > Windows Server 2008 > JDK 9.0.1 > Reporter: Paul Carroll > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9526) Mixed domain tests are launching legacy slaves using current jboss-modules.jar

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9526?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9526: ---------------------------------------- A proposed fix for WFLY-9325 would result in the legacy jboss-modules.jar not being available for mixed-domain (since it would skip extracting anything in the legacy zip's bin folder to disk.) If we fix this and that's in place, we can just change to not extracting bin/client. > Mixed domain tests are launching legacy slaves using current jboss-modules.jar > ------------------------------------------------------------------------------ > > Key: WFLY-9526 > URL: https://issues.jboss.org/browse/WFLY-9526 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Priority: Minor > > DomainTestSupport.Configuration.getSlaveConfiguration(String hostConfigPath, String testName, String hostName, WildFlyManagedConfiguration baseConfig, boolean readOnlyHost, boolean debug) drops any configured jboss.home from the passed in baseConfig, which results in the default one being used. That's fine for the normal testsuite/domain in wildfly core and full wildfly, as all the domain processes in those test modules use the same installation, just with different writable dirs per HC. But in mixed domain it means the legacy slaves are using jboss-modules.jar from the current version, not their own. > This is a minor bug as it seems to not cause any harm, but it could blow up somehow if something changes, and regardless it's not right to run a legacy slave that's not really running legacy software. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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 November 2017