Skip to content

Conversation

@stephenkilbourn
Copy link
Collaborator

This change utilizes the new auth/tenants/writeable endpoint created in feat: add list tenants with create/update scopes endpoint to determine the allowed tenants for the logged in user instead of looking in the keycloak session's scope.

A new Next.js pass-through endpoint is created called /api/allowed-tenants/ which is called with the user's jwt. The returned endpoints are placed in the TenantContext provider. from their, previous behavior is as before:
if no tenants or an api error occurs, the tenant dropdown is hidden and the user can not add a tenant to an ingestion request. if tenant's are returned, then an ingestion request can be made with the user's tenants.

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

Successfully merging this pull request may close these issues.

2 participants