Onboarding to a Centralized Cloud Console
search cancel

Onboarding to a Centralized Cloud Console

book

Article ID: 260874

calendar_today

Updated On:

Products

Protection Engine for Cloud Services

Issue/Introduction

You want to use the centralized cloud console, so referring to the KB Unable to onboard Protection Engine scanners to centralized cloud console., using the .slf license file and the completed form.
First name: user
Last name: example
Email: [email protected]
Company: --
Country: Poland
Address 1: XXX 56
Address 2: 
City: Poznan
State: XX
Zip: XXXX
Phone: +48 xxx xxx xxx
Industry: IT Security
Site ID/support ID: 4xxxxxxx
Serial Number: B8xxxxxxxxx
 
Content of the license file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<licenses xmlns="https://licensing.symantec.com">
<license signature="">
<license_format>1</license_format>
<fulfillment_id>---------</fulfillment_id>
<serial_id>--------</serial_id>
<serial_number>B--------917</serial_number>
<product_name>Symantec Protection Engine for Cloud Services Not For Resale License</product_name>
<site_id>41xxxx9</site_id>
<transaction_type>6.0</transaction_type>
<sign_date>2022-12-21</sign_date>
<key>
<name>SAVSE40 AntiVirus</name>
<version>8.0</version>
<count>20</count>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>Scan Engine URL Filtering</name>
<version>8.0</version>
<count>20</count>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>SAVSE40 AV Content</name>
<version>8.0</version>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>Scan Engine URL Content</name>
<version>8.0</version>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>SPEInsightReputation</name>
<version>8.0</version>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>SPEAPKReputation</name>
<version>8.0</version>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>SPEDeepSight</name>
<version>8.0</version>
<count>20</count>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
<key>
<name>SPEDeepSight Content</name>
<version>8.0</version>
<start_date>2022-12-20</start_date>
<end_date>2024-12-31</end_date>
<warn_policy>1,60</warn_policy>
<grace_policy>1,0</grace_policy>
<license_type>NOT-FOR-RESALE</license_type>
<license_meter>User</license_meter>
<product_type>Subscription</product_type>
<order_type>New</order_type>
</key>
</license>
</licenses>
 
But the issue is the SPE onboard does not appear when the customer login into this link (https://securitycloud.symantec.com/cc/#/landing). They can see the WSS and DLP cloud consoles, but not the one for SPE as per below in the screenshot:-
 
 

Environment

Release : 8.2.2

Resolution

Raise a case to Customer Support Engineers Contact Broadcom support and with the help of Customer Support who will raise a Jira case on the other hand to the Development team (Customer Response Engineering) will help in setting the right privileges to your CWP cloud, In more detail: 

The above error occurred because user "[email protected]" didn't have access to the SPE Cloud console. Instead, the user "<username>@<yourdomain.com>" had access to the SPE cloud console.

Add user "[email protected]" to the SPE cloud console. User "[email protected]" would have then received the activation email -->You need to click on the "activate" button to activate the cloud console. Once activated, the user will be able to log in to the SPE Cloud console.

If you want the access to be given to a different user, once you log in to the CWP portal using the above email id, You can add other users from the settings -> Users -> Add User.