Repository navigation
Password history policy - add time based policy - #30215
Conversation
89c6420 to
3383ec5
Compare
3383ec5 to
c7b8445
Compare
c7b8445 to
12713ef
Compare
|
Implementation is based on other password history based policy - HistoryPasswordPolicyProvider.java |
There was a problem hiding this comment.
Just a few nitpicks - otherwise LGTM
9a93123 to
5f58de0
Compare
|
Updated branch with suggested changes. I also increased the time offset in tests, it was set to a couple of seconds, but now it is a couple of minutes. It should help with test flakiness in case of longer runs. |
6b903ab to
5d1d62a
Compare
21f7e9d to
8c66df9
Compare
|
Hi everybody, imo the feature is ready to go. It looks like all tests are green. One issue I have is that I changed documentation which triggers the documentation validation job. There are some expired links, but it's not in caused by my changes. Looks like it's the scope of a different task. |
8c66df9 to
0ab59b9
Compare
|
Hi, looks like the pipeline is green. My tests are run in job: Keycloak CI / Base IT (6) |
047270c to
0ffcd47
Compare
0ffcd47 to
259ef3e
Compare
|
Hi, are there any additional steps I have to take to get this merged/released? No additional activity from me, except rebasing. |
2bbc368 to
f10f835
Compare
|
Hi, looks like the feature works, all tests are passing, there is documentation ready in PR, and the only issue is the amount of changes coming to the main branch and rebasing it. |
|
Hi @sguilhen pinging for visibility, I saw you assigned this task to yourself. I implemented the changes you suggested: #30215 (comment) |
|
Hi @MaciejMierzwa - yeah, I assigned it to myself to ensure I can help drive this to completion. I've already asked for maintainer approval for the PR, I'm hoping to get this in shortly |
Closes keycloak#30210 Signed-off-by: Maciej Mierzwa <dev.maciej.mierzwa@gmail.com>
Signed-off-by: Pedro Igor <pigor.craveiro@gmail.com>
f10f835 to
223b5d8
Compare
There was a problem hiding this comment.
@MaciejMierzwa Thanks for your time. I have just updated the docs to make it a bit more clear about the intention of the new policy.
Please, let me know what you think. LGTM.
Issue: #30211
Discussion: #30210
Closes #30211