Hi Yufei,

+1 on the idea. Putting `allowedRealms` on the profile and letting
the deployment admin set it seems like a clean way to handle the
realm side.

If it's left unset, existing names keep working as they do today.
If it's set, only the listed realms can use the profile.

As JB mentioned, a catalog admin would still need a privilege to use
it.

Thanks,
Vignesh

On Tue, 17 Nov 2026 at 06:08, Yufei Gu <[email protected]> wrote:

> JB, Prithvi, I’m fine keeping #5664 focused on SigV4 signing using the
> existing names and configuration as I explained in my original email.
>
> Dmitri, good point to revisit the secrets manager discussion. Listing
> credential
> profiles would be part of that discussion.
>
> Vignesh, good point on realm-specific profiles. Should we make realm scope
> part of the credential profile, perhaps through an allowedRealms property
> controlled by the deployment admin? That would define which realms may
> reference the profile.
>
> Yufei
>
>
> On Sat, Nov 14, 2026 at 1:26 PM Prithvi S <[email protected]>
> wrote:
>
> > Hi Yufei,
> >
> > You're right, that is a bit tricky. I felt the same while writing
> > #5664. Asking the deployment admin for a name every time doesn't
> > really work if they aren't the same person.
> >
> > I'd like this PR to stay with the #3409 names for SigV4 signing,
> > same flag, keys on the server. How about listing the names someone
> > is allowed to use, and a privilege on them, as a follow-up? Wdyt?
> >
> > Thanks,
> > Prithvi
> >
>

Reply via email to