[2.4] Add warning when the same admin in project.yml has different role #2469
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.
Description
By design, provisioners can add clients or admins in project.yml and do provision to get additional client/admin startup kits. The certs and private keys of existing participants are kept the same so that there is no need to re-distribute those existing startup kits.
When the role of existing admin changes in project.yml, its cert/private key and thus the role in subject's unstructured_name, do not change. This causes confusion as provisioners may think a new set of cert/private key is generated.
This PR adds a warning during provisioning time so that provisioners know what to do to generate the new startup kits.
Types of changes
./runtest.sh
.