Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Can there be 2 Authentication Provider in 1 Knox Topology?

Solved Go to solution
Highlighted

Can there be 2 Authentication Provider in 1 Knox Topology?

Expert Contributor

Can I configure two authentication provider for Knox and if how would that work?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Can there be 2 Authentication Provider in 1 Knox Topology?

As far as I know, up to Knox-0.6 (currently used in HDP) there can be only one Auth. provider per topology. Last time when I faced such a requirement I created two topologies, one for each Auth. provider.

Edit: KNOX-236 is going to provide such a feature but "in the future".

2 REPLIES 2

Re: Can there be 2 Authentication Provider in 1 Knox Topology?

As far as I know, up to Knox-0.6 (currently used in HDP) there can be only one Auth. provider per topology. Last time when I faced such a requirement I created two topologies, one for each Auth. provider.

Edit: KNOX-236 is going to provide such a feature but "in the future".

Re: Can there be 2 Authentication Provider in 1 Knox Topology?

It is technically possible to have more than one authentication provider in a given topology but the result is unlikely to be what is expected. The first reason might be that all but one of them is enabled=false so that there is in effect only one. The other possibility is that a given custom service in a topology requires a specific authentication provider implementation. In this case the first enabled authentication provider in the topology would be the default and the custom service would identify a specific authentication provide by role and name in its service.xml file.