zoom_in Click to enlarge

Jenkins Active Directory Plugin

▲ ▼

Jenkins CI CD Security Enterprise Microsoft Authentication Active Directory

language

description Jenkins Active Directory Plugin Overview

The Jenkins Active Directory Plugin automates user and group provisioning within an Active Directory environment, synchronizing users and groups between Jenkins and AD based on defined rules and configurations for continuous integration/continuous delivery pipelines.

help Jenkins Active Directory Plugin FAQ

Does the Jenkins Active Directory Plugin work on Windows and Linux?

Yes, the plugin supports both environments, but its connection behavior differs. On Windows, a domain-joined Jenkins machine can use ADSI, while non-Windows installations generally require an Active Directory domain and LDAP or DNS configuration.

Can Jenkins use Active Directory groups for permissions?

Yes, Jenkins recognizes the Active Directory groups associated with authenticated users. Those groups can then be used with authorization systems such as matrix-based security.

Which ports are commonly used by the Jenkins Active Directory Plugin?

Typical LDAP connections use port 389, while LDAP over SSL commonly uses port 636. Global Catalog lookups use 3268 without SSL or 3269 with SSL.

What happens if Active Directory becomes unavailable?

The plugin can be configured with a fallback user that remains available when communication with Active Directory fails. Since plugin version 2.5, that fallback account can continue administering Jenkins during an AD outage.

swap_horiz

Looking for Jenkins Active Directory Plugin alternatives? Compare top competitors ranked & scored

arrow_forward