Hi Robert,
check the "ldap_settings" collection in MongoDB and make sure that only 1
entry exists in there.
Cheers,
Jochen
On Thursday, 2 June 2016 15:07:37 UTC+2, Robert Hough wrote:
>
> Unable to locate said user in those areas. For the sake of clarity;
> this account was initially used
Unable to locate said user in those areas. For the sake of clarity; this
account was initially used to setup LDAP, but was done so in error. LDAP
was then reconfigured with the correct credentials. It's like Graylog has
somehow held onto this incorrect ldap configuration, somewhere, but I
Thanks I'll check on this in the morning and see if that clears up the
issue. It isn't a huge concern as I plan to rebuild the stack once I've
got everything as I like it, but just wanted to make sure it was something
I could clear up later.
On Friday, May 27, 2016 at 8:34:54 PM UTC-4,
Hi Robert,
please try deleting the "user_redacted" user (either in the web interface
on the System -> Users page or in MongoDB in the "users" collection).
Cheers,
Jochen
On Saturday, 28 May 2016 02:34:54 UTC+2, Robert Hough wrote:
>
> 2016-05-28T00:28:12.333Z ERROR [LdapUserAuthenticator]
Hi Jochen,
Thank you for your assistance. I have successfully configure ldap
authentication for Graylog2.
Tom
On Tuesday, March 29, 2016 at 6:45:59 AM UTC-4, Jochen Schalanda wrote:
>
> Hi Tom,
>
> that usually shouldn't happen. Please check the ldap_settings collection
> in your MongoDB
Hi Tom,
that usually shouldn't happen. Please check the ldap_settings collection in
your MongoDB database and either remove all documents in that collection or
all but the most recent one:
- https://docs.mongodb.org/getting-started/shell/client/
-
