Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.1.0
Description
Kerberos Identity data is empty when Cluster.security_type does not equal "KERBEROS".
Technically this seems to make sense since there shouldn't be any relevant Kerberos identities if the cluster isn't configured for Kerberos; however a chicken-and-the-egg condition is encountered when manually enabled Kerberos and a listing of the needed Kerberos identities is needed before Kerberos is to be fully enabled.
Solution
Allow the keberos_identities API end points to generate data even if Cluster.security_type is not equal to "KERBEROS".
Attachments
Attachments
Issue Links
- links to