Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TREP APIs /
  • Open DACS /
avatar image
Question by sergey.emantayev · Jul 13, 2019 at 12:16 PM · opendacsloginopendacs-api

OpenDACS: Should I check daemonConnectionState before calling login()?

Following AuthorizationSystem::createAuthorizationAgent(), our code is monitoring AuthorizationAgent::daemonConnectionState() before calling login(). It proceeds to login() only after the state comes to authorizationConnectionUp. However the documentation does not mention checking the state. Sometimes the state is still authorizationConnectionPending even few seconds after the createAuthorizationAgent call. Is it mandatory to check the daemon connection state before calling login()? Is it safe to call login() if the state is still pending?

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by jirapongse.phuriphanvichai · Jul 15, 2019 at 02:39 AM

Yes, the code should check the daemonConnectionState before login().

If the application calls the login when the daemonConnectionState is not up, it may receive the following events.

12:13:21 Received DACS Authorization Event... 
User: user01 Position: 10.0.0.1/net 
Status: LoggedOut 
Status Code: AuthorizationSystemNotAvailable 
Status Text: DACS_UserLogin: Can't login User due to DACS Multiplexer connection down 
DACS Event stream closed 

The event stream has been closed so the application needs to login again to open the stream.

In my opinion, it is not mandatory to check the daemon connection state before calling login() but it is nice to check it to avoid the re-login.

It is safe to call login() if the state is still pending. The key point is that the application needs to handle the stream state properly and check that if the login is opened/closed and LoggedIn/LoggedOut.

Comment
sergey.emantayev

People who like this

1 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
6 People are following this question.

Related Questions

Opne DACS Java API - Restrict a user to login more than once from same position.

Unable to download OpenDacs SDK - What means ReLoginUserPass?

Where can i check open dacs rest api request/response structure. for example http:///command=peCheck&service=IDN_SELECTFEED&domain=LONDON_TEST&user=DIALG&position=1.1.1.1/net≈plication=312&peset=18446744073709551391,9580

Assertion failed: pDacsSystem != NULL

Changing entitlements via OpenDACS

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges