Support Center

Configuring Apache Archiva to use JumpCloud's LDAP-as-a-Service

Prerequisites:
See Using JumpCloud's LDAP-as-a-Service to obtain the JumpCloud specific settings required below.

When using Apache Archiva's LDAP integration, here are the basic settings to configure authentication with JumpCloud's hosted LDAP service:
 

General:


host: ldap.jumpcloud.com
port: 389 (StartTLS) or 636 (SSL)
Writable LDAP: <leave unchecked>

baseDn: ou=Users,o=<your-organization-id>,dc=jumpcloud,dc=com
Base Dn for groups: ou=Users,o=<your-organization-id>,dc=jumpcloud,dc=com
bindDn: uid=<ldap-binding-user>,ou=Users,o=<your-organization-id>,dc=jumpcloud,dc=com
password: <ldap-binding-user's-password>
ssl enabled: <checked if using port 636 for "port">
Enabled LDAP authentication: <checked>

 

Properties (Tab 1):


ldap.bind.authenticator.allowEmptyPasswords: false
ldap.config.dn: dn
ldap.config.groups.class: groupOfNames
ldap.config.groups.member: member
ldap.config.mapper.attribute.email: mail
ldap.config.mapper.attribute.fullname: cn
ldap.config.mapper.attribute.password: userPassword



 

Properties (Tab 2):


ldap.config.mapper.attribute.user.id: uid
ldap.config.mapper.attribute.user.object.class: inetOrgPerson
ldap.config.max.result.count: 0
ldap.config.user.attribute: uid


 
 

Last Updated: Oct 03, 2016 01:42PM MDT

Related Articles
desk-forwarding@jumpcloud.com
http://assets3.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete