![]() |
|
|
|
|
Change By:
|
ssbarnea
(12/Jul/13 5:43 PM)
|
|
Description:
|
Crowd authentication worked perfectly until we moved jenkins to another domain.
The "funny" part is the if I check the logs jenkins says that the user was authenticated but in fact the login button does nothing.
Temporarly we switched back to LDAP authentication, which BTW worked without any problem.
Clearly there is something that prefect crowd2 from saving the authentication.
{code}
<authorizationStrategy class="hudson.security.AuthorizationStrategy$Unsecured"/>
<securityRealm class="de.theit.jenkins.crowd.CrowdSecurityRealm" plugin="crowd2@1.5">
<url>https://crowd.domain.com/crowd</url>
<applicationName>jenkins</applicationName>
<password>pass</password>
<group>jira-users</group>
<nestedGroups>false</nestedGroups>
<sessionValidationInterval>60</sessionValidationInterval>
</securityRealm>
{code}
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
