Est subsystem deplyment change #5169
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EST subsystem has been modified to use the security domain during the deployment and this is the default behaviour. Installing with SD the EST subsystem will use the subsystem certificate to communicate with the CA. An additional subsystem user is created when deployed in a separate instance. Alternatively, standalone 2 step installation is provided and in this case the sslserver and subsystem certificate have to be generated during installation. EST cannot create its own SD since the related APIs are not present.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the other change to EST subsystem the deployment has been modified to work like other subsystem, in particular TPS.
The certificates for EST are obtained from the CA after security domain registration. The EST communicate with the CA using the subsystem certificate and it is associated to the "Certificate Manger Agents" role.
The CA administrator has the role for "Enterprise EST Administrators".
The est profile is associated to the new role and it is enabled but not visible by default.
Standalone 2-steps installation is supported as well as the previous installation with certificates provided in a p12.
Test have been updated for the new approach.