Open DACS behavior when number of simultaneous login
I have a user logged in with position `X` and number of simultaneous login allowed is set to `1`. What happens in following cases -->
1. Same user tries to login again with same position
2. Same user tries to login with different position . Will new login be blocked or old user will be automatically logged out?
Best Answer
-
Thank you for reaching out to us.
I tested those cases and got the following results.
1. Same user with the same position can login properly
2. Same user with the different postion can't login and the error is Access Denied: already using position 10.0.0.1
However, you may need to contact the DACS support team directly via MyAccount to confirm this behavior.
09:31:39 Received DACS Authorization Event...
User: User1 Position: 10.0.0.1/net
Status: Loggin
Status Code: NoStatusCode
Status Text: LoginResultPass: handle[1]
09:31:43 authorizationAgent::login() succeeded
09:31:44 Received DACS Authorization Event...
User: User1 Position: 10.0.0.2/net
Status: LoggedOut
Status Code: LoginDenied
Status Text: Access Denied: already using position 10.0.0.1
DACS Event stream closed
09:31:50 authorizationAgent::login() succeeded
09:31:50 Received DACS Authorization Event...
User: User1 Position: 10.0.0.1/net
Status: Loggin
Status Code: NoStatusCode
Status Text: LoginResultPass: handle[3]1
Answers
-
Open DACS behavior when number of simultaneous login
I have a user logged in with position `X` and number of simultaneous login allowed is set to `1`. What happens in following cases -->
1. Same user tries to login again with same position
2. Same user tries to login with different position . Will new login be blocked from or old user will be automatically logged out?
In Open DACS with a simultaneous login limit set to
1
, here's how it behaves:Same User, Same Position: If the same user tries to log in again from the same position, the new login attempt will be blocked. The user will be unable to log in again from the same position.
Same User, Different Position: If the same user tries to log in from a different position, the new login attempt will typically block the old session. The original session will be automatically logged out locksmith to allow the new login.
This behavior ensures that only one active session per user is permitted at any time.
1
Categories
- All Categories
- 6 AHS
- 37 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛