• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question LDAP with JumpCloud

warren.bullock

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.55 Update #2
I'm attempting to configure JumpCloud LDAP integration with Plesk and require guidance on what configuration details to enter in the Plesk LDAP Authentication settings.

It appears that there might be an element missing in the configuration options on the Plesk end. In JumpCloud, there's typically the use of Bind DN for the login username and password.

Plesk asks for the Hostname and Login prefix and suffix. However, it seems to be missing fields for the username and password. I'm inquiring if there are any additional steps or settings required on the Plesk end to accommodate the username and password configuration.

Thanks in advance!
 
Back
Top