Amir Zarrinkafsh

@davama how'd you go with testing this, with the updated filter did it prevent you from being able to login with that user? Just want to understand current behaviour so...

I don't think that's entirely related, we could handle a different message in this scenario like we do when we identify that the new requested password doesn't fit the policy...

I believe this needs to be modified slightly because you should be looking at the status code received from `haproxy-auth-request` which is stored as `txn.auth_response_code`.

Apologies for missing this @Cajuteq there hasn't been any discussion about this outside of this specific thread. Per @james-d-elliott's earlier commentary: > I think in general this idea is good,...

You can exclude the location(s) in the respective queries.

We have been tracking upstream. Currently to support this we're awaiting the following PR to be merged: https://github.com/fasthttp/session/pull/47.

@Ohelig please feel free to PR said changes to the docs, I think it'd be a very welcome addition.

Some examples have been provided so I'm going to close this issue. If you're still having issues please explain what you have tried and we may be able to assist.

The opt-in nature kind of goes against the principle of security through notification. What's your thoughts around how the opt-in would work? I think long term if a user can...

There's nothing harmful in the presented changes, I would suggest removing all the newlines and commentary for each option though. Remember this file is only provided as a baseline because...