Skip to content
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

Allow for passing tenant in query parameter #22

Open
davidspek opened this issue Apr 13, 2023 · 0 comments
Open

Allow for passing tenant in query parameter #22

davidspek opened this issue Apr 13, 2023 · 0 comments

Comments

@davidspek
Copy link
Contributor

Currently if the X-Scope-OrgID header is already present in the request to Oathkeeper, the permission check endpoint in ouir backend will only check if the subject can access that tenant and return only 200 or 403 (without including the header in the response). This means it does not resolve all tenants a subject can access. This can be useful in cases where federated request across multiple tenants aren't supported or wanted.

However, in cases such as the Alertmanager UI, which doesn't support tenant federation, it will be difficult to add headers to requests. To solve for this use case we should allow passing a tenant ID as a query parameter. Then our permission check endpoint can check if the query parameter is present. If it is, it can check that the subject has the permissions to access the Alertmanager UI and finally add the X-Scope-OrgID header in the response so it can be passed along downstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant