KEY_RING specification for Vantage StoragePoint web client.

Products

• Vantage Storage Resource Manager

Issue/Introduction

Can you provide more details about the keyring owner specification for Vantage StoragePoint web client?

Is READ access to keyring sufficient for the Vantage StoragePoint owner? does it imply that SSL logic of encrypt/decrypt itself is the application’s responsibility and not some function of TCPIP internally? 

Resolution

1. Keyring specification consists of //KEY_RING_OWNER/KEY_RING_NAME.
2. The KEY_RING_OWNER should be the ID of the user that runs the Apache Tomcat server (Vantage StoragePoint web client started task usually VANWEBUI).
3. The Vantage StoragePoint started task owner (same user ID) must have READ access to the keyring where the certificate is stored.
4. When we are configuring the Keyring used by Tomcat connector (Vantage StoragePoint web client application), the TLS handshake and encryption / decryption will be responsibility of the Tomcat web container.

More details can be found in Vantage tech doc for Configure Vantage StoragePoint™ Web Client to Use HTTPS.

The above documentation also explains how to set up the HTTPS configuration for the Tomcat connector after installation.
If you prefer, you can configure the same server.xml file to run the connector in plain HTTP mode without a TLS certificate.
However, be aware that in this case, communication between your web client and the server will not be encrypted or secured by TLS.