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] Read and use SSH keys stored in Active Directory #3141

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

[RFE] Read and use SSH keys stored in Active Directory #3141

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2099

  • Created at 2013-09-25 12:34:13 by mkosek
  • Closed at 2020-03-24 14:18:11 as wontfix
  • Assigned to nobody

Add support SSH key management in Active Directory and use the SSH keys in existing SSSD SSH integration feature.

We can enhance SSSD to fetch the keys from AD and store in the SSSD cache on the IPA
servers and distribute to the IPA clients via the LDAP exop that is already used to make the AD users available to the clients.

Recommended practices: http://tools.ietf.org/html/draft-ylonen-sshkeybcp-01 [[BR]]
Related freeipa-users thread: http://www.redhat.com/archives/freeipa-users/2013-September/msg00265.html

Comments


Comment from dpal at 2013-09-26 15:31:54

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred


Comment from dpal at 2013-09-26 15:32:11

Fields changed

rhbz: => todo


Comment from mkosek at 2017-02-24 14:25:02

Metadata Update from @mkosek:

  • Issue set to the milestone: SSSD Patches welcome

Comment from pbrezina at 2020-03-24 14:18:10

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.


Comment from pbrezina at 2020-03-24 14:18:12

Metadata Update from @pbrezina:

  • 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
Projects
None yet
Development

No branches or pull requests

1 participant