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

Keep .pem format for truststore #6807

Open
2 tasks done
planetf1 opened this issue Aug 15, 2022 · 3 comments
Open
2 tasks done

Keep .pem format for truststore #6807

planetf1 opened this issue Aug 15, 2022 · 3 comments
Labels
enhancement New feature or request pinned Keep open (do not time out) security Security related (high priority)

Comments

@planetf1
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Please describe the new behavior that that will improve Egeria

When configuring Jupyter/Python, the root & intermediate certificates need to be available in the cert store
These tools require .pem format not .p12

Rather than doing the conversion when the container is launched, the appropriate format should be one of the outputs from
the gensamplecerts.sh script

In fact the 'tmp.pem' is exactly the right file to use as it is a) unprotected (Fine for a trust store) and b) contains both the root & intermediate certs and c) is in PEM format

Therefore the fix is purely to add docs & to rename this file to something sensible.

Alternatives

No response

Any Further Information?

No response

Would you be prepared to be assigned this issue to work on?

  • I can work on this
@planetf1 planetf1 added enhancement New feature or request triage New bug/issue which needs checking & assigning labels Aug 15, 2022
@planetf1 planetf1 self-assigned this Aug 15, 2022
@planetf1 planetf1 added the security Security related (high priority) label Aug 24, 2022
@planetf1 planetf1 removed the triage New bug/issue which needs checking & assigning label Sep 30, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Nov 30, 2022
@planetf1 planetf1 removed the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Nov 30, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Jan 30, 2023
@planetf1 planetf1 removed the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Feb 6, 2023
@github-actions
Copy link

github-actions bot commented Apr 8, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Apr 8, 2023
@planetf1 planetf1 removed the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Apr 14, 2023
@planetf1 planetf1 removed their assignment May 15, 2023
@mandy-chessell mandy-chessell added the pinned Keep open (do not time out) label Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned Keep open (do not time out) security Security related (high priority)
Projects
None yet
Development

No branches or pull requests

2 participants