:
Subject: Re: Nifi Registry LDAP
So interesting thing just happened. I added my TLS parts of the
identity-provider.xml and I restarted the server and everything is working fine.
I don’t want you digging into it too much but it is a strange issue I was
receiving.
On Apr 10, 2018, at 3:21
w...@mobilgov.com>>
> Reply-To: mailto:users@nifi.apache.org>>
> Date: Tuesday, April 10, 2018 at 16:05
> To: mailto:users@nifi.apache.org>>
> Subject: Re: Nifi Registry LDAP
>
> I was able to remove the TLS information in the identity-provider.xml and was
>
16:05
To:
Subject: Re: Nifi Registry LDAP
I was able to remove the TLS information in the identity-provider.xml and was
able to use my remote LDAP to login. So I think I am narrowing down the issue.
On Apr 10, 2018, at 2:57 PM, Kevin Doran wrote:
Thanks Scott,
I don’t see
tion. I created a free
> jumpcloud account, so I’ll try to recreate this issue and get back to you if
> I have any other insights.
>
> Kevin
>
> From: Scott Howell
> Reply-To:
> Date: Tuesday, April 10, 2018 at 15:54
> To:
> Subject: Re: Nifi Registry LDAP
>
: Nifi Registry LDAP
I was able to switch back to my local LDAP server and was able to login
successfully. The provider I am using in identity-providers.xml is as follows:
ldap-identity-provider
org.apache.nifi.registry.security.ldap.LdapIdentityProvider
SIMPLE
I was able to switch back to my local LDAP server and was able to login
successfully. The provider I am using in identity-providers.xml is as follows:
ldap-identity-provider
org.apache.nifi.registry.security.ldap.LdapIdentityProvider
SIMPLE
cn=Manager,dc={redact
Thanks Kevin for sending that back,
This is what I see when looking at the Headers on the login.
The version of Nifi-Registry I am running is 0.1.0. What confuses me is that
this was working with my local LDAP fine. It just stopped working when I
switched to setting up the identity-provider.x
If everything is configured correctly, this error usually indicates that the
server did not locate your login credentials when processing the login request.
That usually means it will not even attempt to authenticate the credentials, so
I'm not sure it is an LDAP configuration error.
If you
Yes I changed that from USE_DN to USE_USERNAME to do some troubleshooting.
Sorry for not changing it back before I sent this stuff out.
> On Apr 10, 2018, at 2:01 PM, Mike Thomsen wrote:
>
> Scott,
>
> In your last email, the way I read it you found part of the problem was using
> USE_USERNAM
Scott,
In your last email, the way I read it you found part of the problem was
using USE_USERNAME and not USE_DN, have you done a full comparison of the
other config with this one?
On Tue, Apr 10, 2018 at 2:58 PM, Scott Howell
wrote:
> Yes I did, I had Nifi-registry working with a local instanc
Yes I did, I had Nifi-registry working with a local instances of LDAP running.
It’s now not cooperating since I moved to using Jumpcloud.
> On Apr 10, 2018, at 1:56 PM, Kevin Doran wrote:
>
> Hi Scott,
>
> Did you configure nifi-registry.properties with:
>
> nifi.registry.security.identity.p
Hi Scott,
Did you configure nifi-registry.properties with:
nifi.registry.security.identity.provider=ldap-identity-provider
On 4/10/18, 14:53, "Scott Howell" wrote:
Thanks for the all the help yesterday standing up LDAP for NIFI. I was able
to troubleshoot and fix the issues myself. I am
Thanks for the all the help yesterday standing up LDAP for NIFI. I was able to
troubleshoot and fix the issues myself. I am running into a unique issue with
my Nifi-Registry when I try to login with my LDAP credentials like I do for the
nifi cluster I get in my logs with this:
2018-04-10 18:43:
13 matches
Mail list logo
