You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ For Windows:
107
107
108
108
5\. Follow section Securing access to Active Directory servers to enable LDAPS
109
109
110
-
Disaster recovery: In case that after all of this you cannot login anymore, you should enable the logging on the plugin to understand why it is failing. In case that after you enable the secured option you cannot login on the instance anymore, you might want to quickly fallback to the previous status specially on production environments. You can easily do this by going to $JENKINS\_HOME/config.xml and under the section \<securityRealm class="hudson.plugins.active\_directory ActiveDirectorySecurityRealm" revert the tlsConfiguration to the previous status. A restart is needed.
110
+
Disaster recovery: In case that after all of this you cannot login anymore, you should enable the logging on the plugin to understand why it is failing. In case that after you enable the secured option you cannot login on the instance anymore, you might want to quickly fallback to the previous status specially on production environments. You can easily do this by going to $JENKINS\_HOME/config.xml and under the section \<securityRealm class="hudson.plugins.active.directory.ActiveDirectorySecurityRealm" revert the tlsConfiguration to the previous status. A restart is needed.
@@ -157,12 +157,12 @@ To verify if the connection is upgraded or not, see [Logging](https://www.jenkin
157
157
158
158
On the other hand, if you wish on using LDAPS, you should set:
159
159
160
-
- System property `-Dhudson.plugins.active\_directory.ActiveDirectorySecurityRealm.forceLdaps=true` as a startup parameter to force Jenkins to start a connection with LDAPS.
160
+
- System property `-Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true` as a startup parameter to force Jenkins to start a connection with LDAPS.
161
161
- Use secured port is defined 636 or 3269
162
162
(`your.hostname.com\[\|:636\|:3269\]`)
163
163
164
164
Note that
165
-
`-Dhudson.plugins.active\_directory.ActiveDirectorySecurityRealm.forceLdaps=true` skips the default LDAP + TLS upgrade.
165
+
`-Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true` skips the default LDAP + TLS upgrade.
166
166
167
167
#### Override domain controllers
168
168
@@ -247,4 +247,4 @@ See the [changelog](https://github.com/jenkinsci/active-directory-plugin/blob/ma
247
247
248
248
## Release Notes
249
249
250
-
See [Github Release](https://github.com/jenkinsci/active-directory-plugin/releases).
250
+
See [Github Release](https://github.com/jenkinsci/active-directory-plugin/releases).
0 commit comments