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

Thanks, Anca!

Istvan