Re: Finding realm identifier in authorization calls

[Alexandre Dutra]

Hi Madhan,

Right now, I think you need to inject RealmContext into your
PolarisAuthorizerFactory. It's fine to inject a request-scoped bean in
an application-scoped bean, as long as the request scope is active
when the bean is accessed – which will be the case when the create()
method is invoked.

Thanks,
Alex

On Thu, Apr 9, 2026 at 3:40 AM Madhan Neethiraj <mad...@apache.org> wrote:
>
> Authorizer instances are created per request with following call to the 
> registered factory:
>
>
>
>   PolarisAuthorizer PolarisAuthorizerFactory.create(RealmConfig config);
>
>
>
> RealmConfig doesn’t have any methods to obtain realm identifier. How does an 
> authorizer implementation find the realm identifier? Perhaps it’s the name of 
> the ROOT entity in PolarisResolvedPathWrapper object given to the authorizer 
> in authorizeOrThrow()? I find this name to be “root_container” in my tests.
>
>
>
> Thanks,
>
> Madhan
>