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

Support access to hasura console for all roles #587

Open
revskill10 opened this issue Sep 30, 2018 · 1 comment
Open

Support access to hasura console for all roles #587

revskill10 opened this issue Sep 30, 2018 · 1 comment
Assignees
Labels
a/authz Issues related to "authorization" and the policy engine after session claims are procesed a/cloud c/console Related to console c/server Related to server k/enhancement New feature or improve an existing feature k/production Related to production use-cases p/longterm Low priority issues that will be picked up based on user feedback or bandwidth s/triaged This has been reviewed by Hasura v2

Comments

@revskill10
Copy link

revskill10 commented Sep 30, 2018

Currently Hasura only allows access to console for admin role.
We also need to have access to hasura console for all roles.
User could use a JWT token as password to access console.

All action/permissions are provided by admin.

@shahidhk shahidhk added k/enhancement New feature or improve an existing feature c/console Related to console labels Oct 1, 2018
@karthikvt26 karthikvt26 added the p/longterm Low priority issues that will be picked up based on user feedback or bandwidth label Oct 9, 2018
@dsandip dsandip added the k/production Related to production use-cases label Feb 12, 2019
@rikinsk-zz rikinsk-zz added the c/server Related to server label May 7, 2019
@vaishnavigvs vaishnavigvs added a/authz Issues related to "authorization" and the policy engine after session claims are procesed a/cloud labels Jun 25, 2021
@manasag manasag added v2 s/triaged This has been reviewed by Hasura labels Dec 27, 2023
@manasag
Copy link
Contributor

manasag commented Dec 27, 2023

Console depends on Metadata API call for many basic functionalities; for which admin secret in required. At this point, this is not planned to be supported due to architecture limitations.

hasura-bot pushed a commit that referenced this issue May 20, 2024
<!-- Thank you for submitting this PR! :) -->

## Description

These files have been moved to `crates/schema`, don't know how they
ended up back. Functional no-op.

V3_GIT_ORIGIN_REV_ID: 0cdda71476e84f06c5adab9273c08c843a6f945e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/authz Issues related to "authorization" and the policy engine after session claims are procesed a/cloud c/console Related to console c/server Related to server k/enhancement New feature or improve an existing feature k/production Related to production use-cases p/longterm Low priority issues that will be picked up based on user feedback or bandwidth s/triaged This has been reviewed by Hasura v2
Projects
None yet
Development

No branches or pull requests

8 participants