Support #6838

LTER user can't log in

Added by Jing Tao over 5 years ago. Updated about 5 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Estimated time:


marco: should still work
[4:32pm] Jing: but why the search doesn’t work?
[4:32pm] Jing: and i can’t log in it from knb web page.
[4:34pm] marco: my guess is that the connection is trying to connect to 389, which IIRC is where startTLS initiates
[4:34pm] marco: port 389 is now blocked - not my decision
[4:34pm] Jing: aha.
[4:35pm] Jing: thanks, marco
[4:35pm] marco: if necessary, 389 can be opened for a specific IP or range
[4:35pm] marco: and startTLS enabled
[4:37pm] marco: we'll work with mark schildhauer next week to figure out the disposition of LDAP


#1 Updated by ben leinfelder about 5 years ago

Sounds like we need to follow-up with Mark Servilla about opening LDAP port to their server from KNB IP address (

#2 Updated by Matt Jones about 5 years ago

I am dealing with James on other firewall and LDAP issues now as we transition the LTER LDAP and personnel databases to the Network Communications Office at NCEAS. James already opened the LDAP system to the NCEAS subnet, and I will request that he opens it to the DataONE and NCEAS subnets in the North Hall Data Center as well.

#3 Updated by ben leinfelder about 5 years ago

  • Target version changed from 2.5.0 to Unspecified
  • Status changed from New to In Progress
  • Tracker changed from Bug to Support

Looks like this is not a Metacat bug and should not delay 2.5 release.

Also available in: Atom PDF