-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPAL Agent does not receive data source configuration after scope update #779
Labels
bug
Something isn't working
Comments
Here the entire log (was too long for a single message):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When an OPAL Agent is configured to use scopes and connects to an OPAL Server without any scopes being configured, it receives the default data and policy source configuration, which is expected but not useful. However, after configuring a scope via the OPAL Server
/scopes
endpoint - including both policy and data source configurations - the OPAL Agent only receives the policy source configuration for its scope, the data source configuration is however not propagated, causing all OPA authorization requests to fail due to missing data.To Reproduce
/scopes
endpoint, including both a policy source and a data source./v1/data
endpoint of OPA and observe, that there are no entries related to data which should actually have been fetched from the above said data sources.Here the excerpt forom the docker compose yaml file related to agent and server config:
And here the document sent to the
/scopes
endpoint after both, the agent and the server are started:Expected behavior
When a scope is configured via the /scopes endpoint, the OPAL Agent should receive both the policy source and data source configurations.
OPAL version
The text was updated successfully, but these errors were encountered: