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

Issue 5038 - BUG - dsconf tls may fail due to incorrect cert path #5039

Merged
merged 1 commit into from Nov 30, 2021

Conversation

Firstyear
Copy link
Contributor

Bug Description: Early in lib389 startup, certain functions are not
available, especially in dsconf. This means we can't read the live value
for the certdir, and we haven't overriden in it the container
so dsconf tls fails.

Fix Description: Apply the manual container path consistent with
other overrides

fixes: #5038

Author: William Brown william@blackhats.net.au

Review by: ???

Bug Description: Early in lib389 startup, certain functions are not
available, especially in dsconf. This means we can't read the live value
for the certdir, and we haven't overriden in it the container
so dsconf tls fails.

Fix Description: Apply the manual container path consistent with
other overrides

fixes: 389ds#5038

Author: William Brown <william@blackhats.net.au>

Review by: ???
Copy link
Contributor

@progier389 progier389 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Firstyear Firstyear merged commit 051b9fb into 389ds:master Nov 30, 2021
@Firstyear Firstyear deleted the 5038-getcert-dir branch November 30, 2021 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dsconf instance tls may fail in a container due to paths not being initialised early in lib389
2 participants