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

[MISC] Catch OpenLDAP ppolicy error #1508

Merged
merged 6 commits into from
Dec 16, 2020
Merged

Conversation

nightah
Copy link
Member

@nightah nightah commented Dec 3, 2020

Further to the discussion over at #361, this change now ensures that OpenLDAP password complexity errors are caught and appropriately handled.

This change also includes the PasswordComplexity test suite in the LDAP integration suite. This is because a ppolicy has been setup and enforced.

@authelia
Copy link

authelia bot commented Dec 3, 2020

Artifacts

These changes are published for testing on Buildkite and DockerHub.

Docker Container

  • docker pull authelia/authelia:misc-openldap-ppolicy-support

@codecov
Copy link

codecov bot commented Dec 3, 2020

Codecov Report

Merging #1508 (82d4300) into master (f2282f7) will increase coverage by 0.04%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1508      +/-   ##
==========================================
+ Coverage   66.75%   66.79%   +0.04%     
==========================================
  Files         144      144              
  Lines        3976     3981       +5     
  Branches      169      169              
==========================================
+ Hits         2654     2659       +5     
  Misses       1113     1113              
  Partials      209      209              
Flag Coverage Δ
backend 67.39% <100.00%> (+0.05%) ⬆️
frontend 64.60% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
internal/handlers/handler_reset_password_step2.go 57.69% <100.00%> (+3.52%) ⬆️
internal/utils/strings.go 90.00% <100.00%> (+0.81%) ⬆️
web/src/services/Api.ts 96.87% <100.00%> (ø)
web/src/services/Client.ts 61.11% <100.00%> (ø)
web/src/views/ResetPassword/ResetPasswordStep2.tsx 67.24% <100.00%> (ø)

Copy link
Member

@james-d-elliott james-d-elliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the only thing. Think we're introducing a regression if we choose the current method.

internal/handlers/handler_reset_password_step2.go Outdated Show resolved Hide resolved
@nightah nightah marked this pull request as draft December 3, 2020 22:40
@nightah nightah marked this pull request as ready for review December 4, 2020 01:16
web/src/services/Client.ts Outdated Show resolved Hide resolved
Copy link
Member

@james-d-elliott james-d-elliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly a what do you think? I'm happy to go ahead if you think it's not valuable.

internal/handlers/const.go Outdated Show resolved Hide resolved
web/src/services/Client.ts Outdated Show resolved Hide resolved
web/src/services/Api.ts Outdated Show resolved Hide resolved
Further to the discussion over at #361, this change now ensures that OpenLDAP password complexity errors are caught and appropriately handled.

This change also includes the PasswordComplexity test suite in the LDAP integration suite. This is because a ppolicy has been setup and enforced.
Copy link
Member

@james-d-elliott james-d-elliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nightah nightah merged commit 7c6a868 into master Dec 16, 2020
@nightah nightah deleted the misc-openldap-ppolicy-support branch December 16, 2020 01:30
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.

None yet

3 participants