WrenSecurity/wrenam

Authentication chain is not updated immediately

Closed this issue · 2 comments

fyrbach commented

Authentication chain update will not take effect until Wren:AM restart.

Steps to reproduce:

  1. Run clean Wren:AM with default configuration
  2. Create new authentication chain (e.g. "demo") in top level realm
  3. Add modules "Data Store" and "HOTP" into that chain
  4. Try login using this chain (http://.../auth?service=demo)
    • An user "demo" with password "changeit" can be used
    • User has to pass both auth. modules
  5. Remove "HOTP" module from auth. chain
  6. Try login using the chain again
    • User still has to pass both auth. modules

Expected behavior:

Changes in authentication chain will take effect immediately after save.

fyrbach commented

This issue is caused by WrenSecurity/wrends#69.

pavelhoral commented

I was not able to replicate the issue with the current version with upgraded Wren:DS dependency.