Community Articles
Find and share helpful community-sourced technical articles.
Cloudera Employee
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loginIdentityProvider': FactoryBean threw exception on object creation; nested exception is java.lang.Exception: The specified login identity provider 'kerberos-provider' could not be found.

CloudBreak 2.7 built HDF 3.1 has error: 'kerberos-provider' could not be found.

The reason is HDF 3.1's blueprint has problem:

nifi.security.user.login.identity.provider= is set to kerberos-provider but that provider doesn't exist in login-identity-providers.xml, or is commented out

1,172 Views
0 Kudos
Comments
Rising Star
@Zhen Zeng

To create an HDF cluster with Cloudbreak, a KDC must be configured, unless you have registered an LDAP in Cloudbreak and select that when creating the cluster. During cluster creation, did you use test a KDC or an existing KDC?

For configuring Cloudbreak to create a cluster that uses a KDC, please refer to the Enable Kerberos documentation for Cloudbreak 2.7.

For complete instructions to create an HDF cluster with Cloudbreak, please refer to the Cloudbreak 2.7 documentation for Creating HDF Clusters.

Cloudera Employee

Hi @Jeff Storck,

Thanks for telling me this.

> To create an HDF cluster with Cloudbreak, a KDC must be configured

After using a test KDC , the CB 2.7 can provision HDF 3.1 successfully.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.
Version history
Last update:
‎10-08-2018 06:45 AM
Updated by:
Contributors
Top Kudoed Authors