New Buypass SEID2 root certs for test #35
Merged
Conversation
This file contains 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
Long story. We originally acquired the certs they published valid from nov. 3rd 2020, but they got replaced shortly after. digipost/api-client-shared-dotnet#30 (comment) This is possible due to the root certificate, which is self-signed, is created from the same keys, and the already issued intermediate certs will still validate as issued by the (new) root cert. This is OK, due to these certs are solely for use for testing, and does not constitute any authority for actual identification of parties.
hanskhe
approved these changes
Jan 3, 2024
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.
We originally acquired the certs they published valid from Nov. 3rd 2020, but they got replaced shortly after.
digipost/api-client-shared-dotnet#30 (comment)
This is possible due to the root certificate, which is self-signed, is created from the same keys, and the already issued intermediate certs will still validate as issued by the (new) root cert. This is OK, due to these certs are solely for use for testing, and does not constitute any authority for actual identification of parties.