Skyhigh Cloud Connector Known and Resolved Issues

March 11, 2022

When LDAP/LDAPs server connectivity is interrupted in AD integration, Skyhigh Cloud Connector may not fetch all users. As a workaround:

1. Stop CC service (./shnlpcli stop)
2. Take a backup of Idapusers directory from CC installation directory. For example, <CC installtion directory>\leveldb\ldapusers>
3. Delete the ldapusers directory
4. Start CC service (./shnlpcli start)

March 8, 2022

When Active Directory custom attributes are configured on Skyhigh Cloud Connector, you might fail to upload or partially upload sanction users. As a result, users are unable to create any User Groups.

This issue is now fixed.

Feb 24, 2022

When the split health notification for File Processing Status is enabled, it sends an email alert if any issues are identified. Once these identified issues are resolved, the users do not receive the normal status email notification alert.

This issue will be fixed in an upcoming release.

Feb 16, 2022

If you have configured Skyhigh Cloud Connector old notifications alert from the Settings > Global Notifications page or User Menu > Notification Settings page and you might fail to enable new split health notifications. As a workaround, delete the Overall Health notification from the old notification alert to configure the new split health notification.

Dec 13, 2021

When the users search for user names in plain text with the uppercase (for example, GUEST) from Omnibar, Skyhigh Cloud Connector displays errors and does not provide any results. 

This issue will be fixed in an upcoming release. 

Oct 21,2021

While running Quality Check for log parser wizards: Import Existing Configuration and Manual Configuration, you might encounter improper results. Because currently on the Sub Configuration page, the fields Preprocessor Class Name supports only the Rule-Based Preprocessor option, and the File Format supports only the Bluecoat option. If you select other options from the list besides the specified options on the Sub Configuration page, you will find invalid results.

This issue will be fixed in an upcoming release. 

After upgrading Skyhigh Cloud Connector from 5.2.2 to 5.4.2, CC may fail to start. If you see these two errors, PANHostname and proxyBypass, use the following steps:
 

For PANHostname:

• Delete the three entries within logprocessor.db.script and logprocessor.db.script.save files corresponding to the PAN settings.
• Restart the CC.

For proxyBypass:

Run the following CLI command:

./shnlpcli sp --name proxyBypass --val true --encrypt"

For help, contact Support. 

Even when all Cloud Connectors are configured with AD, the following message appears in Infrastructure > Cloud Connector > Custom Attributes: 

"You have more than 1 instance of Cloud Connectors and it is recommended to configure Custom Attributes on all the instances that are processing logs to ensure consistency of data fetched and processed. Please set up Custom Attributes for all symbolic servers."

This issue will be fixed in an upcoming release. 

The date format doesn't automatically pick the selected Timestamp column from the Map Log Fields in the Log parser when there are multiple date header columns such as Date or Timestamp in the parsed logs. As a workaround, make sure to manually update the correct date format. 

Cloud Connector throws ldapusers cache error after upgrading from 3.9.2 to 5.3.0 and above versions. As a workaround:

1. Delete the ldapusers cache from the Cloud Connector installed directory (leveldb) and restart the Cloud Connector.
2. Use the following curl command to push respective properties to YML with the mentioned payload when switching between rocksdb and leveldb:

Switching to leveldb

{
  "logProcessor":{ "unmatchedtracker.keyValueStoreType":"LEVELDB",
  "ldapusers.cache.type":"LEVELDB","dualmode.storeType":"LEVELDB",
  "tldcache.cache.type":"LEVELDB","ipDomainCache.cache.type":"LEVELDB",
  "blockedURLCache.cache.type":"LEVELDB",
  "ipUserMapperStore.cache.type":"LEVELDB"   },
  "integration": {
    "smtp": {},
    "siem": {},
    "panorama": {},
    "custom_attributes": {},
    "ip_user_mapping": {},
    "syslog": {}
  }
}

Switching to rocksdb

{
  "logProcessor":
  { 
  "unmatchedtracker.keyValueStoreType":"ROCKSDB",
  "ldapusers.cache.type":"ROCKSDB","dualmode.storeType":"ROCKSDB",
  "tldcache.cache.type":"ROCKSDB","ipDomainCache.cache.type":"ROCKSDB",
  "blockedURLCache.cache.type":"ROCKSDB",
  "ipUserMapperStore.cache.type":"ROCKSDB"   },
  "integration": {
    "smtp": {},
    "siem": {},
    "panorama": {},
    "custom_attributes": {},
    "ip_user_mapping": {},
    "syslog": {}
  }
}

RocksDB is not the default cache memory when Skyhigh Cloud Connector is upgraded from 5.0.1 to 5.3.0 version. As a workaround, you need to explicitly configure levelDB to RocksDB.