If you do not specify a salt-index or iteration-count-index, I believe it will assume the column is in modular crypt format and it should just work.
17:42:28,328 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 3) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("jdbc-realm" => "DatabaseRealm")
]) - failure description: "WFLYCTL0155: 'salt-index' may not be null"
Maybe need to use a different kind of password mapper for MCF encoded passwords?
The underlying mapper definitely supports it. However, looking at the resource, it appears that the "salt-index" and "iteration-count-index" both are non-optional and have a minimum value of 1. This seems like a bug to me: the JDBC password mapper definitely allows these fields to be optional. Could you please open an issue here: JBoss Issue Tracker
There was discussion about BCrypt recently . With conclusion bcrypt mapper expects Base64 format to be stored in DB.
So should be JIRA created with this two requirements?:
- make bcrypt mapper work with MCF (not only Base64)
- make bcrypt mapper work just with 1 password column (no need for salt and iteration count columns)