-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
GEN-927 - Add bot default roles #18256
Conversation
@@ -1488,8 +1495,9 @@ && userHasRelationshipWithAnyBot(original, bot)) { | |||
original.getAuthenticationMechanism()); | |||
user.setRoles(original.getRoles()); | |||
} | |||
// TODO remove this | |||
// TODO remove this -> Still valid TODO? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@harshach not sure what was the context on this TODO. Is it still valid?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets remove it
authMechanism = original.getAuthenticationMechanism(); | ||
} | ||
} | ||
case SSO -> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since we now only support the UI to create JWT bots, took the chance to remove this case
Quality Gate passed for 'open-metadata-ingestion'Issues Measures |
* GEN-927 - Add bot default roles * GEN-927 - Add bot default roles
Describe your changes:
Fixes GEN-927
DefaultBotRole
that is added to any bot created. It contains theDefaultBotPolicy
andDataConsumerPolicy
. Without it, newly created bots did not have any kind of access to the data on a default installation of OM.DomainOnlyAccessRole
so that unless admins change it, that bot can only access its own dataType of change:
Checklist:
Fixes <issue-number>: <short explanation>