Reference Guide

Login security settings
The initial login to SNOW instance is handled by SNOW .The connection with the OME/SAE instance are done with respective
credentials. Session or token based authentication is used to communicate with OpenManage and SupportAssist Enterprise.
Network security
The communication from OMISNOW application happens two ways:
1. The SNOW instance communicates with MID server using ECC queue.
2. The OMISNOW connector jar(MID server) communicates with OME and SAE using HTTPS.
NOTE: User is given an option to approve SSL certificate. Once its approved, the certificate will be installed in the trust
store which is used in all the subsequent calls.
Validating jar file
Jar file validation is performed to check the integrity of the file.
jarsigner.exe - verify [OMISNOW jar path]
Path of jarsigner : C:\Program Files\Java\jdk-<version>\bin>jarsigner.exe
If jar is signed we will get message jar verified ,else jar is unsigned
Table 3. Lists of ports
Communication Channel Port number
ECC 443
HTTPS 443
Data security
● The monitoring data is fetched from OME and the data is stored in SNOW CMDB. Data is secured by SNOW.
● The OpenManage Enterprise and SupportAssist Enterprise user credentials are encrypted and stored in SNOW CMDB.
● The data which is in the transit through OMISNOW is secured by HTTPS.
Signature file verification
Signature file verification is used to verify the integrity of the update set xml file.
About this task
Following are the steps to verify signature file:
Steps
1. Download GPG3 public key from http://linux.dell.com/files/pgp_pubkeys/0x1285491434D8786F.asc).
2. Import the public key in the system using GPG. gpg --import 0x1285491434D8786F.asc
3. Upon running gpg --list-key, it lists the key ID 34D8786F.
4. Validate signature file using gpg --verify <FileName>.tar.gz.sign <FileName>.tar.gz or gpg -v --
verify <FileName>.tar.gz.sign <FileName>.tar.gz
Verification is successful if you see the following output:
gpg: Signature made Fri 17 Nov 2017 03:40:10 PM IST using RSA key ID 34D8786F
gpg: using PGP trust model
gpg: Good signature from "Dell Inc., PGRE 2012 (PG Release Engineering Build Group
Product and Subsystem Security
11