Expected format of the parameter position within class StandardPrincipalIdentity

lei.x.zheng
Newcomer
in Open DACS
Within rfa8.2.2.L1.win-shared.rrg\Include\Common\StandardPrincipalIdentity.h
class RFA_COMMON_API StandardPrincipalIdentity : public PrincipalIdentity
{
/** Set Position (This is the position in the context of Refinitiv Data Access Control System) */
void setPosition( const rfa::common::RFA_String & position );
}
- If we pass in position as an IP address e.g. “192.168.0.10”, the OpenDACS login is always denied without a meaningful log message in dacs.snkd.log
- If we pass in position as an IP address with / e.g. “192.168.0.10/”, the OpenDACS login is successful with a position as “192.168.0.10/net” in dacs.snkd.log
- If we pass in position as an IP address with HostName e.g. “192.168.0.10/HostName”, the OpenDACS login is successful with a position as “192.168.0.10/HostName” in dacs.snkd.log
- If we do not pass in position, the OpenDACS login is successful with a position as “1.1.1.1/net” in dacs.snkd.log
From the testing results listed above, it seems the parameter position is just looking for a /. Without /, the login is always denied without a meaningful log message. If nothing is provided after /, then it would be defaulted to /net. Otherwise, if a string (such as HostName) is provided after /, then it would use the string provided, i.e. / HostName
- Would you please clarify if the above understanding on the expected format of the parameter position is correct?
- What is the expected string after / for the parameter position? Is it HostName?
- If nothing is provided after /, why is it defaulted to /net?
- It seems position is optional, as if no position is provided, then it is defaulted to 1.1.1.1/net?
- Should the user rely on the current behavior (that providing / is a must, without a / the login is always denied)? Do you have any plan to change the expected format of position in the future?
Tagged:
0
Best Answer
-
Hi @lei.x.zheng,
The position parameter is of the format - IP Address/Hostname or Network Mask.
The position parameter is optional, and any value can be passed within it, if your DACS administrator hasn't enforced a specific IP check. If it is not enforced, then it is used for logging purposes.
0
Categories
- All Categories
- 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
- 613 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
- 248 ETA
- 552 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
- 630 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
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛