IDS User Authentication - Token Generation

According to documentation, "IDS typically uses Token authentication, which means, IDS clients setup a
mechanism of authenticating and generating token for end users. This token is
used by IDS to verify user entitlements against DACS. The mechanism of token
generation is up to clients. It can be a custom app which maintains a database
of users, or a plugin which can integrate with domain servers like Active
Directory."
Do we have any details on how to set up token generation? Thanks,
Best Answer
-
Hello,
Reposting the answer worked out off-line by the user @billy.w.cunningham,
So other users can be informed:
"
You must specify a user name in
the Token field. IDS and DACS handle this correctly. GOOD USER, GOOD RICcurl http://localhost:8080/ids-rest/json/quote/IDN_SELECTFEED/TRI.N?token=u189984
"
0
Answers
-
Hello @billy.w.cunningham,
If you are an application developer, your application would receive the generated token during the authentication step, and then pass it into consecutive data request step(s).
If you are trying to set this up correctly on your IDS, per installation guide, "the default authentication plug-in provided in the package simply assumes that the received token is the DACS ID". If you are looking to set up a different mechanism, we may be able to better help by connecting you with the right contact in TR.
You may wish to follow-up with more info, on what you are trying to do?
0 -
Thanks for your reply Zoya. We are trying to set up web based data delivery, and authenticate users in the simplest way possible. Do I understand correctly that a login ID will be assumed to be the DACS username, and passed to DACS automatically?
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 中文论坛