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
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛