[
https://issues.jenkins-ci.org/browse/JENKINS-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Busha resolved JENKINS-12683.
---------------------------------
Fix Version/s: current
Resolution: Not A Defect
My apologies, this was a configuration error. The alias I was using to access
Jenkins did not resolve to the fully qualified name, just the machine name. The
user authenticated correctly with Crowd, but the cookie (for the domain) didn't
match Jenkin's address (machine name). Thanks for the help!
> Crowd 2 plugin authenticates, but doesn't allow login
> -----------------------------------------------------
>
> Key: JENKINS-12683
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12683
> Project: Jenkins
> Issue Type: Bug
> Components: crowd2
> Affects Versions: current
> Environment: x64 Windows 7
> Reporter: Dan Busha
> Assignee: Thorsten Heit
> Priority: Critical
> Labels: plugin, windows
> Fix For: current
>
>
> I have an installation of Jenkins 1.450 with the Crowd 2 plugin v1.4
> installed connecting to a Crowd v2.4.0 server which successfully
> authenticates users (according to the log). When a user enters their username
> and password and clicks 'log in' they are returned to the main Jenkins page
> but are not logged in.
--
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
