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] Allow BIND without a target entry #593

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

[RFE] Allow BIND without a target entry #593

389-ds-bot opened this issue Sep 12, 2020 · 4 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/593

  • Created at 2013-02-21 01:15:12 by nkinder (@nkinder)
  • Closed at 2020-04-22 16:35:39 as wontfix
  • Assigned to nobody

Allow authentication without an entry

  • If just using the directory server for authentication, want to allow the directory server to authenticate identities
  • This is mostly applicable for non-password based auth, or cases where the directory server is not the credential store
  • For example, cert based auth; SASL auth (GSSAPI, other cases where you pass off the auth decision to sasl), PAM pass through, other types of pass through auth
  • In this case, you want to allow the auth even if there is no user entry
  • this probably wouldn't work for simple auth (no user entry to retrieve userPassword from)
  • Need to be able to use access control, resource limits, groups/roles, CoS, with these user identities
@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 22:57:38

Metadata Update from @nkinder:

  • Issue set to the milestone: FUTURE

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-04 05:00:29

Is this still relevant @nkinder ?

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-04 05:00:33

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to new
  • Issue close_status updated to: None

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-04-22 16:35:41

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None (was: new)
  • 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