ArcotUserManagementSvc for User Operations in UDS Webservice

Products

• CA Strong Authentication

Issue/Introduction

During the design and build of a AA( Advanced Authentication)  client, while reviewing the two WSDLs ArcotWebFortIssuanceSvc and ArcotWebFortAuthSvc — the following behavior was observed:

• ArcotWebFortAuthSvc:
  After ingestion of this WSDL, the client solution builds successfully. No testing has been carried out at this stage, this was purely a compilation check.

• ArcotWebFortIssuanceSvc:
  After ingestion of this WSDL, the client solution does not build.
  There are references to user-related functions in the existing SSO interface code, but these functions are not present in the new WSDL file.

Specifically, the following user-related functions are missing:

• CreateUser

• DisableUser

• EnableUser

• FetchUser

• UpdateUser

This raised the question:

• Have user-related requests been split into a separate WSDL?

• If yes, customers will need access to that WSDL as well.

Environment

CA Strong Authentication

Cause

From version 6.2 to 7.0, there was a change in how user-related requests are handled:

• User-related operations (CreateUser, DisableUser, EnableUser, FetchUser, UpdateUser) are no longer part of ArcotWebFortIssuanceSvc.

• These operations have been separated into a different WebService: ArcotUserManagementSvc, which is part of the User Directory Services (UDS) webservice.

This separation was done on the SDK side to modularize and streamline the Advanced Authentication web service operations.

Resolution

To manage user accounts, you should use ArcotUserManagementSvc, which is included as part of the UDS webservice.

• Check the installation location for ArcotUserRegistrySvc under the /wsdls directory. 

• This service provides the required user operations (CreateUser, DisableUser, EnableUser, FetchUser, UpdateUser).

• These changes explain the differences noted between the 6.2 and 7.0 WSDLs.

For detailed documentation on managing users and accounts via UDS, refer to the official product documentation: Managing Users and Accounts 

Applications upgrading from older versions must update their integration logic to use ArcotUserManagementSvc for all user management operations. This change impacts SSO interface code or any custom integrations relying on user-related functions previously available in ArcotWebFortIssuanceSvc.

With this change, ensure that user-related operations are redirected to ArcotUserManagementSvc, while other issuance and authentication flows continue to use their respective WSDLs.