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?