Enterprise

1. Introduction

Enterprise represents every customer in ZEDEDA. The ZEDEDA support team will create the Enterprise as part of the onboarding process. The admin and support user accounts are also created as part of the enterprise onboarding. The credentials for the admin account will be passed to the customer and can be used for administrative purposes.
 

2. Enterprise Operations using ZedUI

After you log in to ZedControl:
Step 1 > Click on the Administration (Administration_icon.png) icon to land on the Enterprise section.
 
IAM_3_Screen_1.png
 

2.1. Create

ZEDEDA has control over this operation. You cannot create an Enterprise.
 

2.2. Read

After logging in to ZedControl, the read operation shows the 'Details' section.
 
IAM_3_Screen_2.png
 

a) Details

The field values such as 'Name' and 'Title' along with the description, if any, can be seen.
 

b) Authentication Profile

More details about authentication are provided in the update operation.
 

c) Third-Party Integrations

Starting with ZedControl Release 6.3.0, you can integrate third-party tools such as Splunk with ZedControl. The data of all the events generated within your Enterprise is sent to the configured Splunk.

Starting with ZedControl Release 6.8.0, the Rancher plugin is integrated with ZedControl. You can now create an integration plugin for Rancher where the user can mention Rancher connection details.
 

2.3. Update

After logging in to ZedControl, click on the Administration (Administration_icon.png) icon to land on the Enterprise details section.
 
Update/Edit the 'Details' section using the following steps:
  • Step 1 > Click on the Edit (Edit_icon.png) icon.
Note: Only admin users can access the Edit (Edit_icon.png) option.
  • Step 2 > Edit the realm of your Enterprise if required.
Note: Starting with ZedControl Release 6.12.0, enterprise-level customizations are available for logo, primary brand color, and secondary brand color.
  • Step 3 > Click on the 'Save' button.
  • Step 4 > Under the authentication profile section, you can update the profile from the following available list.
 
IAM_3_Screen_3.png
 
  • Step 5 > If you select 'Custom' under authentication provider, enter the details mentioned in the table below.
  • Step 6 > Click on the 'Save' button.
  • Step 7 > You can add one of the following third-party integrations:
    • Splunk
    • Rancher
 
A_MGFjZjlkZDY2YjhlM2JmOTDLu5b-sfoKJN8mC9QYa8od8ztvD4E7zZuDzbi1rBcGaxnLfSHOaxKCD670Jl8vCA8HsYAtgdXk9huPT1B8wqU43r4jpgOc57G0q8XmRmyU.png
 
Input Field Value
Authentication Provider(*)
Select how to authenticate new users.
  • Azure–use Azure AD credentials
  • Google–use Google enterprise credentials
  • Custom–point to a custom authentication provider
  • ZedControl–authenticate users using ZedControl (local user and password)
Authentication Type(*) Only OAuth is supported as an authentication type currently.
Profile Name(*) Select a name for the custom profile.
Client ID(*) Public identifier of ZEDEDA application as registered in the authentication provider.
Client Secret(*) Client secret as provisioned in the authentication provider. Known only to the server and the client(in this case, ZEDEDA).
OpenID Connect Endpoint(*) The endpoint of the authentication provider. Must be OIDC compliant.
Scope OIDC claims to identify application roles. This is useful when application role management is also done at the OIDC provider. By default, the 'roles' claim is used to pick application roles.
Default Role for New Users(*) If no roles are specified via the 'scope' argument, this role is assigned to all new users authenticated by the OIDC provider.

 

  • Step 8 > Add the third-party integration name.
  • Step 9 > Select the category from the dropdown list:
    • Data
    • Remote Orchestration
  • Step 10 > Select from the dropdown list:
    • Splunk
    • Rancher
  • Step 11 > Click on the 'Save' button.
  • Step 12 > Add more integrations by clicking 'Add Integrations' button.
Note: More details about the third-party integration are covered in section 3 of this document.
 
A_MGFjZjlkZDY2YjhlM2JmOVz32rCY4zBMBDqo-9cCQ0z5IDuv0b6QCKAAnC4A0wbBVuUm3Nv-D90pRzY0fueRRXeZy51-agESgFi_EXcnzuGl9Kg09eOk0qKhy8q66B3R.png
 

2.4. Delete

ZEDEDA has control over this operation. You cannot delete an Enterprise.
 

3. Third-Party Integrations

3.1. Splunk

IAM_3_Screen_6.png

 

3.2. Rancher

  • Step 1 > Click on the Administration (Administration_icon.png) icon.
 
A_MGFjZjlkZDY2YjhlM2JmOaKB8dnSKcb6qyHpNtji-oP9lLufeI90byZPsCntQOuRQSq8LD4EOhLkeDhbhajKBBBMeMrvVxEgF9UBxragxqdIz-8tv02wQX14oFVtGJTz.png
 
  • Step 2 > Click on the 'Add Integration' button.
 
A_MGFjZjlkZDY2YjhlM2JmOXhIUK6ya9reL_DxxIS0wRuC93-hq9To8IsY9Xp58ypOsQvoxYJAGpTtM5tiOzcxhkifEgz5FJ4qRl4cMUV3ZTU8W3KQNohR38xPE0zBd7YM.png
 
  • Step 3 > Add the third-party integration name.
 
A_MGFjZjlkZDY2YjhlM2JmOQrI85IZEPcyyE-QhOyPXip7wh4pYCTe3VVVkIRbcm32wez6mUV_jEdAYuIVVeE40Kmp7yDY81OQheZaw2pIx9RyycK7B36rbARFXmASesmo.png
 
  • Step 4 > Select the category from the dropdown list. In this case, it is 'Remote Orchestration.'
  • Step 5 > Select from the dropdown list. In this case, it is 'Rancher.'
 
A_MGFjZjlkZDY2YjhlM2JmOeBUyobOeLnVA_WaL2JTayPThAA-BfyLdzUdEjSZyTIi0dB_pelItZfZK7PsGAht35BcQK4I1t0fwxPqO_1kETinsJfh9VWA0a8zz6AUEGGc.png
 
  • Step 6 > Select authentication type from the dropdown group list:
    • API Token
    • User Credentials

Select 'API Token' in this case.

 
A_MGFjZjlkZDY2YjhlM2JmObIWlH69jCAmOL8jo4OwcUMLE4J31r9X0saN0tiekmndNbwworDAQHMMcAwWdrSpcy9AtWXC2Mbtr52JbBwNlnjgu2yhUCvjtj327QvDWwlA.png
 
Following steps details how to obtain the 'API Token' from Rancher.
  • Step 7 > Login to the Rancher portal by providing the credentials.
 
A_MGFjZjlkZDY2YjhlM2JmOa3KGhLpkb2o5Znhxa4l0VpzEH0VH57TSJKW-S6abLxD-hh5YWi1pXRx-Nea-kURPA0SwO0wCANndAwXbRN_hNXFYdwk5t70kEL5xQq0UsKj.png
 
  • Step 8 > Click on the user name icon.
 
A_MGFjZjlkZDY2YjhlM2JmOVz99Oufz7zu3yfCndfBFAVMODjZcgqAAPULk-DCN5fRZk2_sspq9GXeWUZiHDfiC9Opz-rfN36qNn6vjC2PI7lunv8Hqi1w2NLD5CZBbcSo.png
 
  • Step 9 > Select 'API & Keys' from the dropdown list.
 
A_MGFjZjlkZDY2YjhlM2JmOX-1EB--harihn4q0-Mk8_6zPX8QtZLleTFzJPVdEtBwPTWOeVNyYWdEpbu-_QXpqcAbon8MEgFBORds4qgeNaH2H3tgKgKwOM0hbwboCQ8F.png
 
  • Step 10 > Click on the 'Add Key' button.
 
  • Step 11 > Provide the necessary values as shown and click on the 'Create' button.
 
  • Step 12 > Copy the 'API Key' generated by clicking the copy symbol as shown.
 
  • Step 13 > Back to ZedControl. Paste the 'API Key' copied from the Rancher portal.
  • Step 14 > Click on the 'Save' button.
 
The added Rancher integration details are as shown below.
 
A_MGFjZjlkZDY2YjhlM2JmOS50OzOrFBbGwmAqScJ2tNE8Wq4K2HXekYI46gaGtn_DAahKuHEle2AVuh32o9u1PBgdK9_mmUcvo9LH4aqPG0k-Fa1IqxNwkfVEEcsawlo2.png
Was this article helpful?
0 out of 0 found this helpful

Articles in this section