Can we confirm if we are now enforcing secret key upon login to Datascope Select?

Wai

Can we confirm if we are now enforcing secret key upon login to Datascope Select?

How can we find this secret key for the client?

Hi Irene,

We gave that a go, however think its a different credential that is needed. Here is the information from the devs:

The Credential Manager is failing to fetch the token to fetch the data from the forex.

We are getting the below error when we try to fetch the FX Token

Failed to acquire access token for service using client credentials flow: IdentityProvider=oauth2. Correlation Id=fb0229cf-8b0a-4c78-838b-faf2725b5c2a, UTC TimeStamp=7/20/2025 11:20:46 PM, Error: Failed to exchange client credentials for token. Response code=InternalServerError, Details: { "statusCode": 500, "message": "Internal server error", "activityId": "6cd894d2-239d-43ab-becf-fd2349161065" }

Can you have a look at this, it might be something for the devs to provide?? It might be an automated change when a change of pw is effected?

Jirapongse

@Wai

Thank you for reaching out to us.

Could you please confirm if this question is about the LSEG DataScope Select - REST API?

I tested the DSS username and password on the DSS REST Tutorials Postman collection. The Postman tutorials still work fine with the current DSS username and password.

You may need to contact the DSS support team directly regarding the DSS secret key.