Error "The anti-forgery token could not be decrypted"

Officially Answered

Comments

5 comments

  • Avatar
    Maxim

    Hi Brallan, 

    We finally identified the cause of this issue. This is not TFS nor Timetracker issue directly, but a combination of both.

    We are using same technology as TFS and we put a security cookie into every request. This cookie can in some cases interfere with TFS cookie. Having Timetracker on the same domain as TFS can cause that cookies are overridden.

    The solution is to change address of Timetracker to something distinct from TFS address.

    Sorry that it took so long.

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Hi Maxim,

    Does this mean, that we need at least two windows server machines? One for running the tfs server and one for the timetracker server?

    Best regards
    Carsten

     

    0
    Comment actions Permalink
  • Avatar
    Maxim

    Hi Carsten,

    Having two machines is not required. You can configure everything on the same machine with different bindings in IIS for TFS and Timetracker applications.

     

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Hi Maxim,

    what do you mean with "different bindings". Can you give me an example, what has to be different?

     

    Carsten

     

     

    0
    Comment actions Permalink
  • Avatar
    Maxim

    Hi,

    For example you have your TFS under this address:

    http://tfs-server-address:8080/tfs

    You can install Timetracker on the same machine where TFS is running with binding

    http://timetracker-server-address:8090/

     

    This will work and this is what I mean with "different bindings", Timetracker and TFS should have distinct addresses.

     

    ---
    Maxim

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk