Markus Hjerto created JENKINS-13058:
---------------------------------------
Summary: E-mail to individuals who broke the build is sent to
wrong address
Key: JENKINS-13058
URL: https://issues.jenkins-ci.org/browse/JENKINS-13058
Project: Jenkins
Issue Type: Bug
Components: active-directory, mail, subversion
Affects Versions: current
Environment: CentOS release 5.8
jenkins v1.455
subversion v1.39
active-directory v1.23
Reporter: Markus Hjerto
Priority: Critical
First of all - this problem occurred, from what I can see in my mail archive,
around March 1st. It could be related to the 1.452 Jenkins update.
When a build fails the emails sent to individuals who broke the build is sent
to the wrong address. The e-mails are sent to
*domainname_usern...@domainname.com* instead of *usern...@domainname.com* or
even better full.email.addr...@domainname.com
I see the following in the logs when a build fails:
{noformat}
WARNING: Credential exception tying to authenticate against DomainName.com
domain
org.acegisecurity.BadCredentialsException: Authentication was successful but
cannot locate the user information for DomainName_UserName
{noformat}
So it seems that the active directory plugin is looking for the wrong username.
It should look up "UserName", not "DomainName_UserName ". When I log in to
Jenkins, I can see in the logs that it looks up "UserName" in AD, which is
correct. I can also see that it is provided with all email addresses, full name
etc. So I guess the AD plugin is working.
I believe the problem is related to the DomainName\UserName format that
Windows/Active Directory is using. Our SVN server is also using AD. When I do a
"svn info" on any resource, the LastChanged Author is "DomainName\UserName".
Could it be that the SVN plugin is "sanitizing" DomainName\UserName to
DomainName_UserName?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
