How to Monitor CA Risk Authentication, UDS and CA Strong Authentication Services

Products

• CA Rapid App Security
• CA Advanced Authentication
• CA API Gateway

Issue/Introduction

In an enterprise environment where CA Strong Authentication, UDS  and CA Risk Authentication are running, customers would like to monitor these services and generate alerts if one of them is down.  Exposed Web Services is a great means to monitor these services. 

How to Monitor CA Risk Authentication, UDS and CA Strong Authentication Services ?

Environment

CA Risk Authentication and CA Strong Authentication 

Resolution

WSDL files that are provided in <ARCOT_HOME>\wsdls directory can be used to send Web Services requests to these back end servers running these services.  These are as follows:

1. Under <ARCOT_HOME>\wsdls\uds (wsdls for UDS),

2. Under  <ARCOT_HOME>\wsdls\riskfort (wsdls CA Risk Authentcation)

3. Under  <ARCOT_HOME>\wsdls\webfort (wsdls CA Risk Authentcation) 

Here are examples for the above  (if the images are small and hard to see then kindly Cntrl + to zoom in) 

a. WSDL Webservice call to Monitor CA Risk Authentication Service. – evaluateRisk()

 

Note that Riskfort's "evaluateRisk" web-service call can used to monitor RiskFort.  Note that the port 7778 and RiskFortEvaluateRiskSvc is being used in the URL. 

b. WSDL Webservice call to Monitor Webfort Service. Call – FetchCredential

Note that WebFort's "FetchCredential" web-service call can used to monitor WebFort.  Note that the port 9744 and WebFortIssuanceSvc is being used in the URL. 

c. WSDL Webservice call to Monitor UDS (User Data Service). Call – getUserStatus.

Note that UDS's "getUserStatus" web-service call can used to monitor UDS.  Note that the port 9080 (port where UDS is installed) and ArcotUserRegistrySvc is being used in the URL.