When doing setup-ds.pl and setup-ds-admin.pl, there should be a way to pass in config files and crypto files so that the directory server uses SSL, the admin server uses SSL, the admin server/console use ldaps:// for the config ds and user/group ds.
I think this ticket should include https://fedorahosted.org/389/ticket/48792 and https://fedorahosted.org/389/ticket/48792 should be closed as a dup.
That is, I should be able to run {{{setup-ds.pl --setupssl}}} and be able to pass in {{{--selfsign}}} or {{{--cert [/path/to/cert.pem|/path/to/nssdb:certnick]}}}
If I pass in {{{--selfsign}}} it will create self signed certs/keys/ca certs like setupssl2.sh. Or, it will allow me to pass in cert/key pem files. Or pass in a pre-created nssdb, and tell me which certs to use.
moving this back to NEEDS_TRIAGE so the new functionality from https://fedorahosted.org/389/ticket/48792 can be discussed
Per weekly ticket triage,
1.3.6. Need to decide if it's opt-in or opt-out. It seems like opt-in is ideal. Along with this, it would be nice to be abel to pass in a cert/key.
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.6 backlog
I think that we can close this, because we have a new python installer on the way that supports this. Alternately, we make this a "request" of the new installer instead.
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to review - Issue close_status updated to: None
Metadata Update from @mreynolds: - Custom field reviewstatus reset (from review)
Metadata Update from @mreynolds: - Issue set to the milestone: FUTURE (was: 1.3.6 backlog)
dscreate now does some of this
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/886
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.