#866 Support TLS_KEY for unlocking password-protected NSS databases
Closed: Invalid None Opened 12 years ago by sgallagh.

Openldap 2.4 added support for using Mozilla NSS for crypto. This means that certificate authority certificates can be read from an NSS database instead of from a flat file on the filesystem. Currently SSSD supports this only if the database does not require a password/pin to access.

We need to implement the TLS_KEY option in SSSD to allow setting a password in sssd.conf to read password-protected NSS databases.


Investigate in 1.7 and see what we should do with it.

milestone: NEEDS_TRIAGE => SSSD 1.7.0

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0

"Nice to have" for 1.9.

blockedby: =>
blocking: =>
rhbz: =>

Fields changed

feature_milestone: =>
resolution: => wontfix
status: new => closed

Metadata Update from @sgallagh:
- Issue set to the milestone: SSSD 1.9.0

7 years ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to 0

7 years ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to 0

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1908

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata