Closed srobier closed 1 year ago
Hi @srobier , our current instances configured with LDAP are currently working. Do you have any logs to help?
Hello Richard, Currently the browser console displays "POST https://myiip/dnsname/graphql" net::ERR_EMPTY_RESPONSE. I understand what that error means, just not sure why when I run a ldapsearch query it returns the expected user data. See below for query run on LDAP server that is successful in returning user information: ldapsearch -x uid=test@test.com -b dc=opencti,dc=com -H ldap://LDAPserverIP:389 -s sub "(objectClass=People)" givenName -D "cn=ldapadm,dc=opencti,dc=com" -W
OCTI log "{"auth":{"email": "testuserone","ip":"::ffff:7.211.0.218","referer":"http://opencti:8080/dashboard"},"category":"AUDIT","level":"error","message":"LOGIN","resource":{"provider":"ldapauth"}}"
Issue has been resolved.
Description
When attempting to log into the OCTI UI using the LDAP configuration the docker container stops and restarts the opencti platform. No logs are captured.
Environment
OS: LINUX (Centos7) OCTI version: 5.5.2 OCTI client frontend Other environment details:
deployed using docker-compose.yml
Reproducible Steps
Expected Output
OCTI should reach out to LDAP server via the client and allow user access into the OCTI platform.
Actual Output
The OCTI Platform container restarts on every attempt to authenticate via LDAP.