SecureSpan Bridge / VPN XML Client: Breakdown of files generated by the SecureSpan Bridge / VPN XML Client

Products

• CA API Gateway

Issue/Introduction

Breakdown of files generated by the SecureSpan Bridge / VPN XML Client

 

Environment

VPN XML Client

Resolution

During the initial configuration of the SSB / XVC, a home directory will be created in the following location:

- WINDOWS: c:\documents and settings\<user>\.l7tech
- LINUX: /home/<user>/.l7tech. The <user> value will be the user directory used to run the SSB / XVC.

Within the .l7tech folder it will contain the following directories and files:

- attachments directory: for storing attachments with SwA webservices.

- certs*.p12 files: these are SSL certificates, that are numbered based on the gateway relationship that owns them. So, if the SSB / XVC has a gateway account with a proxy value of "gateway1", then there will be a file called "certs1.p12", that contains the public cert of the SecureSpan Gateway.

-  key*.p12 files: these are the private keys of the client certificates, again there is only one allowed per gateway account. Once a user has consumed a service with a policy that requires client certificate-based authentication (Client cert, WSS, WS-SC, XML signature/encryption), a signing cert will be downloaded to the SSB / XVC, and stored as key<number>.p12.

- ssgs.xml: this is the configuration file for each gateway account used by the SSB / XVC.

- ssa*.log: these log files are generated over the course of running the SSB / XVC. The content/layout of the logfiles are governed by settings made in the logging.properties file.