crowd authentication suddenly stopped working after chaning the domain of jenkins

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major
    • Component/s: crowd-plugin, crowd2-plugin
    • None
    • Environment:
      jenkins-1522

      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.

        <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>

            Assignee:
            rmangi
            Reporter:
            Sorin Sbarnea
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: