-
Notifications
You must be signed in to change notification settings - Fork 155
Clarify adminconsole certs #2754
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
Conversation
🔍 Preview links for changed docs |
@kunisen : the introduction section of the doc needs to identify and explain also the adminconsole certificate. ![]() |
Adding a note to solve #2754 (comment)
Now that we have a specific cert for adminconsole.... is this text still valid in the Cloud UI certificate section? ![]() Could anyone explain what exactly is adminconsole certificate for? We need to explain the difference between CloudUI and adminconsole certificates properly in the documentation if users need to take care of both. What HTTP endpoint is secured by the CloudUI cert and what HTTP endpoint is secured by the adminconsole cert? cc: @Kushmaro |
Thank you @eedugon! I missed that part and now added the note. [1]Based on the internal sync from @beiske and @AlexP-Elastic, my understanding is:
But if we say
Then it will only cause confusion. ![]() [2]I don't know if this is the best choice. @beiske @AlexP-Elastic and @eedugon please help comment on this. Why we have to have this doc PR? ![]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments added, we need to update the intro to show also the new cert and we need to ensure we explain properly what is the adminconsole certificate for, and what exact HTTP endpoint / URLs is securing.
...e/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md
Outdated
Show resolved
Hide resolved
...e/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md
Outdated
Show resolved
Hide resolved
2. Log out of the Cloud UI and log in again. | ||
3. Verify that you are now using the new certificate chain. There should be no security warnings when you connect to the Cloud UI over HTTPS in your web browser. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this cert is for admin console and NOT for CloudUI, the verification should be through API rest calls, or?
What is the adminconsole certificate for exactly?
Step "3. Verify that you are now using the new certificate chain. There should be no security warnings when you connect to the Cloud UI over HTTPS in your web browser
" looks not valid for this certificate verification.
^^ The previous is valid to validate the Cloud UI certificate, not adminconsole cert.
cc: @AlexP-Elastic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC, this cert is only used for port 12343 (not 12443, which is used as cloud UI cert, and that cert handles both UI and API request). And this cert is only used when 12443 is not accessible, as diagnostic usage for API access. Details in my comment - #2754 (comment)
(I might be wrong - please correct me. I don't have the best wording. But I hope via this doc PR we could find a good wording solution for this and we could have fewer customer cases in the future :) )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, thanks for sharing.
I wouldn't remove then the text about API calls in cloudUI cert, as that cert is actually the one valid for the most common API calls made by our users (on port 12443).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @eedugon for being patient. I added back.
Could you check if this time it looks good from docs perspective please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I think I would remove steps 2 and 3 from To add an Adminconsole certificate from the command line:
and leave the openssl
as the only test option (nobody should be doing this anyway, no reason not add AC cert from the UI unless the UI is down - maybe we can add that)
…stallation/manage-security-certificates.md Co-authored-by: Edu González de la Herrán <[email protected]>
…stallation/manage-security-certificates.md Co-authored-by: Edu González de la Herrán <[email protected]>
HI @AlexP-Elastic @beiske could you kindly review this doc PR so that we could sort this out. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to be clearer that the Adminconsole cert does not support standard use, it's a fallback port only
After the certificates have been installed, connecting securely to {{es}}, {{kib}}, and the Cloud UI or making secure RESTful API calls to ECE should not result in any security warnings or errors. | ||
|
||
Adminconsole certificate | ||
: Used to connect securely to make RESTful API calls. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is right
The Cloud UI certificate is for API and UI calls
The Adminconsole certificate allow secure connection to an alternative API port that can be used in incidents scenario where the UI is down (very rare). We recommend re-using the UI certificate for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @AlexP-Elastic
Updated with the suggestion:
- : Used to connect securely to make RESTful API calls.
+ : This certificate facilitates a secure connection to an alternative API port, which can be used in rare scenarios where the UI is unavailable. We recommend reusing the UI certificate for this purpose.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also @AlexP-Elastic I made the change according based on your 2nd comment - #2754 (comment) too:

(Hard to copy things out and mostly the screenshots is visibly evident enough...)
2. Log out of the Cloud UI and log in again. | ||
3. Verify that you are now using the new certificate chain. There should be no security warnings when you connect to the Cloud UI over HTTPS in your web browser. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I think I would remove steps 2 and 3 from To add an Adminconsole certificate from the command line:
and leave the openssl
as the only test option (nobody should be doing this anyway, no reason not add AC cert from the UI unless the UI is down - maybe we can add that)
Thanks @AlexP-Elastic for your suggestion. I made the corresponding updates based on #2754 (comment) and #2754 (comment). Could you kindly help review again please? ![]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Just added a minor wording suggestions.
...e/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md
Outdated
Show resolved
Hide resolved
...e/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md
Outdated
Show resolved
Hide resolved
…stallation/manage-security-certificates.md Co-authored-by: Edu González de la Herrán <[email protected]>
…stallation/manage-security-certificates.md Co-authored-by: Edu González de la Herrán <[email protected]>
Thank you @eedugon and @AlexP-Elastic again! We will have less SDHs in the future 😄 |
Description
To address issue: #2747
Two main edits:
-----BEGIN RSA PRIVATE KEY-----
(openssl with-traditional
option but not default one) and must not be-----BEGIN PRIVATE KEY-----
, otherwise user will getcert.invalid_cert_chain
error.Adminconsole
cert added in ECE 3.8 (maybe @eedugon I need to raise issue in our internal cloud repo and back port it to 3.8?)Reviewers
Preview
Thank you!