389-ds-base

#50150 Allow creating nss db with the custom issuer data
Closed: wontfix by spichugi. Opened by bsmejkal.

Closed: wontfix
Reopen Issue

Currently the NssSsl class is using hardcoded issuer data when creating nss db, self signed CA etc.
We need to be allowed to insert custom issuer data, because we have to automate a case, where we are testing processing of issuer that has comma in it's name (or presumably other characters that require escaping).

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.1
- Issue tagged with: lib389

@mhonek Is this covered by system TLS policy now? And do we use it?

@mhonek Is this covered by system TLS policy now? And do we use it?

Okay, I commented on the wrong ticket but I can't delete them. RIP.

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.3 (was: 1.4.1)

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

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3209

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None

lib389

None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.