Skip to content

Add access control for functions based on full qualified name#12241

Merged
kasiafi merged 1 commit intotrinodb:masterfrom
kasiafi:335FunctionAccessControl
May 5, 2022
Merged

Add access control for functions based on full qualified name#12241
kasiafi merged 1 commit intotrinodb:masterfrom
kasiafi:335FunctionAccessControl

Conversation

@kasiafi
Copy link
Copy Markdown
Member

@kasiafi kasiafi commented May 4, 2022

This change allows providing access control for Table Functions (#11336) both on system and connector level.
Requested by #11336 (comment)

@@ -525,6 +525,13 @@ void checkCanRevokeRoles(SecurityContext context,
*/
void checkCanExecuteFunction(SecurityContext context, String functionName);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we deprecate or remove this one?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. This will be possible only after all functions gain some namespace, which i guess will happen rather sooner than later, but did not happen yet.

@kasiafi kasiafi merged commit 3553eab into trinodb:master May 5, 2022
@github-actions github-actions bot added this to the 380 milestone May 5, 2022
@mosabua
Copy link
Copy Markdown
Member

mosabua commented May 5, 2022

I assume this does NOT need release notes entry. Looks like it is enabling features later..

@kasiafi
Copy link
Copy Markdown
Member Author

kasiafi commented May 5, 2022

I assume this does NOT need release notes entry. Looks like it is enabling features later..

@mosabua that's right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

5 participants