Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39637

How to remove jsessionid on the url when logging in

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 1.653
      Wildfly 9.0.0.CR2
      Active Directory plugin 2.0
    • Similar Issues:

      Description

      Whenever I login to Jenkins using my AD account, I will be redirected to this url http://serverName:8080/jenkins/;jsessionid=xxxxxxxx.serverName and the page says Not Found.

      How do I eliminate this?

      Referring to the attachment "Capture.PNG", checking that option in Wildfly configuration does not help.

        Attachments

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            Wow I missed comments Sorry about that.

            Show
            danielbeck Daniel Beck added a comment - Wow I missed comments Sorry about that.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            It is a defect, just a duplicate one

            Show
            oleg_nenashev Oleg Nenashev added a comment - It is a defect, just a duplicate one
            Hide
            danielbeck Daniel Beck added a comment -

            This is an issue tracker, not a support site.

            Show
            danielbeck Daniel Beck added a comment - This is an issue tracker, not a support site.
            Hide
            ykchow89 Yun Ken Chow added a comment -

            Hi Oleg Nenashev,

            If that's the case, I'll just have to stick with it first for the time being. Thanks!

            Show
            ykchow89 Yun Ken Chow added a comment - Hi Oleg Nenashev , If that's the case, I'll just have to stick with it first for the time being. Thanks!
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I suppose we will have to upgrade or to build your custom Jenkins core with a patch.
            Currently we do not provide patches for Jenkins 1.x, but the upgrade is mostly safe

            Show
            oleg_nenashev Oleg Nenashev added a comment - I suppose we will have to upgrade or to build your custom Jenkins core with a patch. Currently we do not provide patches for Jenkins 1.x, but the upgrade is mostly safe
            Hide
            ykchow89 Yun Ken Chow added a comment - - edited

            Yes, I am running Jenkins within Wildfly (JBoss). When you mentioned 2.4, is that the version for Jenkins? Is there any fixes for the version (1.653) that I'm using or the only solution is that I'll have to upgrade Jenkins?

            Show
            ykchow89 Yun Ken Chow added a comment - - edited Yes, I am running Jenkins within Wildfly (JBoss). When you mentioned 2.4, is that the version for Jenkins? Is there any fixes for the version (1.653) that I'm using or the only solution is that I'll have to upgrade Jenkins?
            Hide
            oleg_nenashev Oleg Nenashev added a comment - - edited

            Are you running within JBoss? Then it's likely JENKINS-34675, which has been fixed in 2.4

            Show
            oleg_nenashev Oleg Nenashev added a comment - - edited Are you running within JBoss? Then it's likely JENKINS-34675 , which has been fixed in 2.4

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ykchow89 Yun Ken Chow
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: