Client_id, username and Machine ID for RDP API

Hi,
Do you have any documentation on the concept of Machine ID ,client ID and username? I would like to understand:
1) Username: Currently we have a trial account and connect via Postman using an username (my e-mail), password and client ID. These are also the parameters used to generate the authentication Token. What changes when we get a Production account? Is the username still an e-mail address? Or do we need to send the Machine ID (in this format: GE-A-00156333-X-XXX) in the parameter "username"? I have tried it, but with my trial account it only works with the e-mail, not with the Machine ID?
2) Account, Machine ID and Client_ID hierarchy: Regarding API Scope (entitlement), at which level are the entitlements defined? Account Level, MachineID/Username Level or Client ID level?
My question is, a customer (i.e. a bank) having one RDP API Account can have multiple Machine IDs and each Machine IDs can have multiple Client IDs. Is it possible to grant each Machine ID with different entitlements? Can the entitlement be even more granular and have one application ID with more/less scope than another Application ID?
3)Client_ID : overall what is the purpose of having the client ID?
Best regards,
Carlos Feres
Best Answer
-
Regards your MachineID and activation, you should have received an email similar to the one below
I will assume you will have done Step 1 - but can you confirm if you clicked on step 2 and set your (very) long password for the MachineID. If you did not, then please do so before trying the above test.
IF you have done the above and you still cannot test with the MachineID then this will need to be esclated to your account team to investigate why this is the case.
0
Answers
-
Hi @carlos.feres3,
The RDP API Quick Start guide provides some basic definitions around some of the terminology in your questions above.
In general, there are 2 IDs you received, an email ID, and a Machine ID. Both of these ID's are usernames but serve different purposes.
- The email ID is primarily used to access the resources within the API Playground, used for testing purposes such as Postman, etc.
- The Machine ID should be your production ID.
The Client ID is the terminology used within OAuth Password Grant specification. Unfortunately, the name implies yet another ID which is why we refer to it as AppKey (or Application Key). The AppKey is simply used to identify a unique application for tracking purposes. So, a given user can have multiple AppKeys (client_id).
In terms of entitlements, it is based on the username (email ID and Machine ID). So, if you discover you need additional permissions, you would typically include both ID's in your request. That being said, it is entirely possible to have different permissions on the 2 user accounts (email ID and Machine ID), but I would imagine users would typically want to make them the same for testing reasons.
Lots of questions in there so I hope this helps :-)
0 -
Thanks for the explanation. One last question. As I said I tried to request a token using the MachineID as the Username in Postman :
and I get this:
Why is that? Shouldn't this work? I basically need a way of checking with my trial account the setup for the production account. I need to know this as we will code in our software the accepted characters/format for the "Username" parameter.
Thanks,
Carlos
0 -
Hi @carlos.feres3,
Your Machine ID should work within Postman - I just tried mine without issue. The authorization does not distinguish between an invalid ID or an invalid password. When you received your Welcome email, containing your ID's, I believe you need to activate your Machine ID. I don't know the entire process flow but will reach out to a colleague to get his input.
0 -
Thanks, you are right. I have a different password for the Machine ID. It works now with the correct password. Best regards, Carlos
0 -
Hello @carlos.feres3
Thank you for your update.
If the reply above was satisfactory in resolving your query, please can you click the 'Accept' text next to the reply? This will guide all community members who have a similar question.
Thanks,
AHS
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛