No missing token in verify_certificate_exists #80
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
Remove the missing token check from verify_certificate_exists. It was the one place that was not adopted to use blank token as default. Change-Id: Ic192e0699ff32af474976039af08e1503925dfd1 See: 17677ae Fixes: https://pagure.io/dogtagpki/issue/3073 Signed-off-by: Christian Heimes <cheimes@redhat.com>
edewata
approved these changes
Oct 25, 2018
This was referenced Oct 1, 2020
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.
Remove the missing token check from verify_certificate_exists. It was
the one place that was not adopted to use blank token as default.
Change-Id: Ic192e0699ff32af474976039af08e1503925dfd1
See: 17677ae
Fixes: https://pagure.io/dogtagpki/issue/3073
Signed-off-by: Christian Heimes cheimes@redhat.com