Opa should always renew its IDP information #63
Merged
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.
In case the underlying Keycloak instance changes and therefore our saved IdP keys are invalidated, we need to make sure that we can update the value in Opa's vault store.
The authx change allows for us to call authx.auth.add_provider_to_opa again with our bearer token and update the value in vault any time the file
/app/bearer.txt
is found on startup.To test: get a site admin token and save it to a file test.txt. Then run
You should see a log message
Updating our IDP with a new bearer token
at the time you did that. You should NOT see a message following that saysIDP is incorrect: verify that Keycloak is set up and clean/build/compose opa again
.