Add a service layer for password validators.
Basics
Logistics
Basics
Logistics
Description
Environment
None
Activity
Show:
Scott Cantor August 14, 2019 at 3:58 PM
Documentation is in decent shape.
Scott Cantor August 13, 2019 at 7:30 PM
Transform of username was moved into the validators so the extracted value is maintained and so validators can apply different transform rules specific to a back-end.
Scott Cantor August 13, 2019 at 4:02 PM
Some docs are done, I did identify one breaking change, I'm not currently accomodating any custom password validators that were built as webflow actions per the V3 docs. I tended to steer people toward using JAAS for that, I think it's probably an acceptable incompatibility.
Scott Cantor August 12, 2019 at 6:35 PM
Instead of a "dummy" back-end I ported in support for Apache htpasswd files.
In theory I guess we could generate one at install time for basic set up/sanity testing.
Scott Cantor August 12, 2019 at 2:00 PM
Theoretically, but I started caring less about that and more about just fixing the chaining problems.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Scott Cantor
Scott CantorReporter
Scott Cantor
Scott CantorComponents
Fix versions
Created January 8, 2019 at 3:45 PM
Updated March 11, 2020 at 2:10 PM
Resolved August 14, 2019 at 3:58 PM
The password login flow would be more flexible if the back-end validators were more dynamically derived at runtime, making the configuration both reloadable and potentially avoiding the need to duplicate the flow in more exotic scenarios with multiple validators. This should open up the ability to chain validators without using JAAS also.