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] Replace certmap.conf with SASL mapping #591

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

[RFE] Replace certmap.conf with SASL mapping #591

389-ds-bot opened this issue Sep 12, 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/591

  • Created at 2013-02-21 01:04:43 by nkinder (@nkinder)
  • Closed at 2020-04-22 16:32:47 as wontfix
  • Assigned to nobody

The certmap.conf configuration file is error prone to configure. It would make more sense to get rid of it and use our SASL mapping rules when mapping certificates to the BIND target. This seems like the right place to do it since client certificate authentication uses SASL/EXTERNAL.

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

Comment from nkinder (@nkinder) at 2017-02-11 23:11:34

Metadata Update from @nkinder:

  • Issue set to the milestone: FUTURE

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-04-22 16:32:48

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None
  • 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