So I changed two things.
1. I updated the START_TLS
with START_TLS this allowed nifi to connect to Jumpcloud.
2. USE_DN from USER_USERNAME and
everything began to work.
> On Apr 9, 2018, at 3:14 PM, Andy LoPresto wrote:
>
> Scott,
>
> One note is that since you are
Scott,
One note is that since you are using port 389 (plaintext LDAP), your
credentials are being transmitted in cleartext unless you are enforcing
START_TLS, and as there is no truststore populated in your config, it does not
appear you are doing this.
You should read the Jumpcloud
That is what is inside of
> On Apr 9, 2018, at 3:03 PM, Scott Howell wrote:
>
> Yep let me send it over.
>
>
>ldap-provider
>org.apache.nifi.ldap.LdapProvider
>ANONYMOUS
>
>uid=nifi,ou=Users,o={redacted},dc=jumpcloud,dc=com
>
Yep let me send it over.
ldap-provider
org.apache.nifi.ldap.LdapProvider
ANONYMOUS
uid=nifi,ou=Users,o={redacted},dc=jumpcloud,dc=com
FOLLOW
10 secs
10 secs
Scott,
I've never implemented NiFi with JumpCloud, but speculating as to what could be
the cause of your error, it could be the User Search Base/Filter configuration
values. Can you share the contents of your login-identity-providers.xml
(removing any sensitive values such as ldap
I was wondering if there was anyone on the user group that had successfully
integrated their NIFI authentication to work with Jumpcloud LDAP. I have
followed the steps Jumpcloud provides with adding the correct credentials to
the the NIFI login-identity-providers.xml but I am getting an error