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,
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?
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 RIC
curl http://localhost:8080/ids-rest/json/quote/IDN_SELECTFEED/TRI.N?token=u189984
"
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?
