[ https://issues.jboss.org/browse/ELY-1435?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1435: ---------------------------------- Let me state this another way: the JDBC mapper is storing and retrieving binary password components (hash and salt) in standard base 64. This is not the same encoding used by modular crypt. So, if you take those base 64 pieces and concatenate them together with a header, you will not get a valid modular crypt. You'd have to base64 decode each piece to a {{byte[]}}, then construct a password spec, generate a BCrypt password, and then render it as modular crypt to get it in modular crypt format, in order to see the modular crypt version. This isn't a bug; the JDBC realm is simply storing the data in a way that it can recover to a {{byte[]}} again. The bug would be if the byte data loaded from the database did not resolve to a valid BCrypt password, or if the byte data that Elytron generates does not match with the byte data that other tools generate for the same cost, salt, and source password. -- This message was sent by Atlassian JIRA (v7.5.0#75005)