I believe the token is specific to the logged in user.

One way to get the token is from making an HTTP POST request to the /login endpoint with this body:

{
  "username": "my_username",
  "password": "my_password"
}

The response body will include a sessionId attribute. The value of that attribute is the token you will want to use.

Hopefully this helps.

Thank you very much, Joseph! I believe we tried this route probably, but I sent it to my team to see if this could work. I'll definitely update you when I hear back!

Hi Joseph,

So we looked into this and the /login endpoint returns a token that is to be used for subsequent requests, but it is not enough for the project links.

In a project link like this: xxx.xxx.com/.../assignments_tasks the 334719763 part comes from the /login endpoint, but we do not know how to generate the dbfca9ff27d8d43f861bdd2b293038efd22c72 part after the underscore.

Best regards

Istvan

That's a good point. Unfortunately, I don't know how to generate the part that comes after the underscore.

Hi Istvan,

As Josepf said, indeed the token can be achieved using the login REST API call. This will be unique for a customer and it also has an expiration time (so the user cannot use it for an indefinite time).

But you are also using the secure Urls option (setting in general.properties file), which means that a hash is added in the Url and ensures the Url is not manipulated manually, an extra security measure added to prevent attacks such as man-in-the-middle.

The way the hash is generated is not exposed to the end user, so unfortunately you cannot generate it.

Thank you,
Anca

Hi Anca,

Very useful, thank you. Indeed it's the secure Url option, if I understand correctly with the secure URL you can even start working without a login.

Best regards,

Istvan

Hi István,

You still need a valid authentication token, otherwise you will have an unauthorized error. The secure Url option will not override any existing security measures, another security layer is added on top of the existing ones.

I want to also mention that in newer WorldServer versions the Urls will look different, as the security was further enhanced. This information might help you in case you want to upgrade to WorldServer 11.8.0 or newer versions.

Thank you,

Anca

Thanks, Anca!

Istvan