|Since version 6 the C++ BCS clients use a new method for login when being connected via WebSockets to BCS. It is an HMAC authorization, which has the advantage that the password is never transferred via network, only a hash value. This method only works if BCS and client use the same DigaSystem registry (Global.par/Rights.par). Therefore, you can use this parameter to choose a different login method for special situations, like when the client uses a different registry as BCS. Hint: so far only DigAIRange supports this parameter. The following options are allowed:
- HMAC: Use an HMAC based authorization.
- AD: Authorize as an ActiveDirectory user. If you explicitly specify "AD", no fallback to HMAC or RC5 is done (in contrast to the default/AUTO behaviour).
- RC5: Cypher the password with the RC5 algorithm. This is the classical/old method used by BCS clients with user name and password.
- AUTO: This is the default. The client will choose the right method automatically, which is: AD if the current user is an AD-synced user, HMAC for a WebSocket connection and RC5 otherwise.
For more information please see: BCSTechManual chapter 8.2.2 "Login to BCS and BUS".