![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
active-directory |
|
Created:
|
19/Apr/13 5:54 AM
|
|
Description:
|
After update to AD plugin 1.31 authentication is no longer working in ADSI mode (i.e. domain name empty in configuration).
Jenkins exception is stating The server is not operational.
When a domain name is set (i.e. in LDAP mode) the authentication is working fine.
But that's not acceptable for me as it will transfer bind passwords in plain text (I didn't yet work on getting Jenkins AD Plugin using LDAPS as ADSI was always working and implicitely uses TLS).
All AD plugin settings are empty. Config section is (actual password replaced by xx)
The problem also occurs of dedicated domain controllers are given.
It only disappears if a domain name is set to force LDAP usage.
Full exception seen is (xx put in place of sensitive AD data):
|
|
Environment:
|
Jenkins 1.511 UE accessed via HTTPS, JRE 1.7.0_07 64bit running on Win7 Pro SP1 64bit.
Multiple slaves, all running Windows 7 or Server 2008.
|
|
Project:
|
Jenkins
|
|
Priority:
|
Blocker
|
|
Reporter:
|
Kurt Loupal
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.