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

RFE - Add socket activated external password syntax checker #2924

Closed
389-ds-bot opened this issue Sep 13, 2020 · 2 comments
Closed

RFE - Add socket activated external password syntax checker #2924

389-ds-bot opened this issue Sep 13, 2020 · 2 comments
Labels
closed: won't fix Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49865

  • Created at 2018-07-20 23:18:43 by mreynolds (@mreynolds389)
  • Closed at 2020-05-06 16:24:23 as wontfix
  • Assigned to nobody

Issue Description

This is being done in FreeIPA, and the idea is you create systemd socket activated script. It could be local or remote(over TLS). Then any kind of custom syntax checker can be used if it follows the protocol. So adding new syntax checks, general maintenance, and customizations are much easier.

This is too much to add to DS for 1.4.0 since are almost out of time, and it is more complex due to DS's local passwords polices (subtree and user policies).

The work being done in FreeIPA is being tracked here:

https://pagure.io/freeipa/issue/5948

@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-02-26 17:08:01

Metadata Update from @mreynolds389:

  • Custom field origin adjusted to None
  • Custom field reviewstatus adjusted to None
  • Issue priority set to: normal
  • Issue set to the milestone: FUTURE (was: 1.4.1)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-05-06 16:24:25

Metadata Update from @mreynolds389:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant