Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Realm Password policies #139

Merged
merged 2 commits into from
Jul 31, 2019
Merged

Conversation

tomrutsaert
Copy link
Contributor

Added Support for password policies.
It checks if the password policy provider is installed.
I did not change or wrap the syntax of the realm password policy string the keycloak API uses.

@tomrutsaert
Copy link
Contributor Author

Some checks were not successful
1 failing and 1 successful checks:
ci/circleci: test-password — Your tests failed on CircleCI

--> These test seem to be flaky, they fail often but not always, the failure has nothing to with my change.

@mrparkers
Copy link
Owner

They are flaky, I can merge this regardless. Thanks for the contribution!

@mrparkers mrparkers merged commit 669ce05 into mrparkers:master Jul 31, 2019
@tomrutsaert tomrutsaert deleted the password-policies branch August 1, 2019 06:57
@timbmg
Copy link

timbmg commented Jun 4, 2020

could your provide an example for this?

@tomrutsaert
Copy link
Contributor Author

tomrutsaert commented Jun 4, 2020

resource "keycloak_realm" "test" {
  realm               = "test"
  enabled              = true
  password_policy = "upperCase(1) and length(8) and forceExpiredPasswordChange(365) and notUsername"
}

The provider uses the same password policy string that keycloak uses itself.

You should always find at least on example for each feature in the example files:
https://github.com/mrparkers/terraform-provider-keycloak/tree/master/example

I should add this to the documentation (I do tend to forget this)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants