Schema Registry Authorization

[Greg Senia]

Is there a known model to provide authorization once authentication passes into schema registry UI/API interfaces. As it's great to have authentication but in a kerberized environment most if not all users will have a kerberos ticket that would be valid so how do you keep users from making destructive changes?

Thanks

[Harsha Ch]

As of current release we only have authentication enabled. Pluggable authorizes with default implementation is on the road map.

Thanks,
Harsha

On Nov 29, 2017, 11:21 AM -0800, Greg Senia <greg....@gmail.com>, wrote:

Is there a known model to provide authorization once authentication passes into schema registry UI/API interfaces. As it's great to have authentication but in a kerberized environment most if not all users will have a kerberos ticket that would be valid so how do you keep users from making destructive changes?

Thanks

--
You received this message because you are subscribed to the Google Groups "Registry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to registry+u...@googlegroups.com.
To post to this group, send email to regi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/registry/950a6077-34b8-4b5e-81bc-8f21db4b682e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.