At a high level, yes, it looks like you're doing everything correctly.  This error message is very explicit and means that Atmos asked the LockBox whether it had a key for your subtenantid/uid and it said no (user does not exist).  A couple things to try:  1) Double check subtenantID and UID.  They are case sensitive. 2) Regenerate secret and try again. 3) If you have multiple tenants, make sure your tenant is assigned to the access node(s) you're hitting.  In this case, the response said that you connected to stlatmos-is1-001. 4) I've also seen this happen when customers have multiple environments (e.g. PROD / TEST / DEV) and accidentally connect to the incorrect environment.  If none of those help, you should open a support ticket to troubleshoot any issues with the subtenant and/or lockbox.
I am trying to connect to our Atmos host, but I am always receiving:  EsuApiLib.EsuException: Unable to retrieve the secret key for the specified user.  I'm pretty confident I'm setting up my connection correctly by specifying subtenant id / uid.  For example, from my screens below: [IMAGE] My code would be (tried both ports 80 and 443, same result):   var api = new EsuApiLib.Rest.EsuRestApi("myUrl", 80, "MySubtenantID/MyUID", "mySharedSecret");  I confirmed that the correct headers are being sent, using Fiddler: [IMAGE] Any ideas why my token ID would not be accepted?
Unable to retrieve the secret key for the specified user while using EsuApiLib