feat(auth): add the GRIMOIRE service permission - #77
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds
GRIMOIREforgrimoire.jorisjonkers.dev. That route sits behind forward-auth, and this entry is its only per-user gate. Without it,fromHostresolves the host to null andverify()lets every authenticated user through. With it, onlyROLE_ADMINand holders ofSERVICE_GRIMOIREget in.ServicePermission.GRIMOIRE("grimoire")ServicePermissionTestresolves the production and local hostnames.ForwardAuthIntegrationTestaddsgrimoireto the hosts a USER without grants is denied.Release
Release auth-api so the deployed enum knows the host before fleet-infra routes
grimoire.jorisjonkers.dev. Pairs with the home-portal change that lists GRIMOIRE in the admin permissions editor.