Skip to content

Commit deaa7d7

Browse files
committed
ENDOC-820 periodic updates
1 parent ef5a0c2 commit deaa7d7

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+569
-563
lines changed

vuepress/docs/next/tutorials/solution/customer-portal.md

Lines changed: 48 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebarDepth: 2
44

55
# Entando Customer Portal
66
## Overview
7-
The Entando Customer Portal enables an organization to quickly provide a modern, self-service, customer-facing application for managing subscriptions. It includes a lightweight integration to Jira Service Management for access to service tickets and a role based access control (RBAC) design for granting users varying levels of access.
7+
The Entando Customer Portal enables an organization to quickly provide a modern, self-service, customer-facing application for managing subscriptions. It includes lightweight integration to Jira Service Management for service ticket tracking and role based access control (RBAC) for a collaborative environment.
88

99
Key Features:
1010

@@ -28,32 +28,36 @@ This tutorial covers:
2828

2929
### Automatic Install via the Entando Hub
3030

31-
#### Integrate the Entando Hub into your App Builder
32-
1. Log in to your `App Builder` and go to `Hub``Select Registry`
33-
2. Choose `Entando Hub` if it has been configured, otherwise:
31+
#### A. Integrate the Entando Hub into your App Builder
32+
1. Log in to your App Builder and go to `Hub``Select Registry`
33+
2. Select `Entando Cloud Hub` if it has been configured, otherwise:
3434
1. Choose `New Registry`
35-
2. In the pop-up window, enter `Entando Hub` and `https://auth.entando.com/entando-hub-api/appbuilder/api` for the URL, then `Save`
36-
3. Click on the Hub in the Registry
35+
2. In the pop-up window, enter the following:
36+
-Name: `Entando Cloud Hub`
37+
-URL: `https://auth.entando.com/entando-hub-api/appbuilder/api`
38+
then click `Save`
39+
3. Click on the Cloud Hub in the Registry
3740

38-
#### Install the Customer Portal
39-
From the Hub Catalog, `Deploy` and `Install` the Customer Portal application first, then the content bundle
41+
#### B. Install the Customer Portal
42+
1. From the Hub Catalog, click the `Customer Portal Application Bundle`, and `Deploy` and `Install` it in the pop-up window.
43+
2. Repeat for the `Content Bundle`. The order is important because the Content Bundle cannot be installed without the Application Bundle.
4044

41-
#### Assign Roles to Configure the Service
45+
#### C. Assign Roles to Configure the Service
4246
1. [Log in to your Keycloak instance](../../docs/consume/identity-management.md#logging-into-your-keycloak-instance) as an admin
4347
2. Give at least one user the ability to manage the Customer Portal:
44-
- Assign the user the `cp-admin` role for the `pn-a71d68dd-166dc0f4-entandodemo-customerportal-server` client.
45-
- See [Role Assignment in ID Management](../../docs/consume/identity-management.md#authorization) for more details.
48+
- Assign the user the `cp-admin` role for the `pn-a71d68dd-166dc0f4-entandodemo-customerportal-server` client. (See [Role Assignment in ID Management](../../docs/consume/identity-management.md#authorization) for more details.)
4649
- Assign the user the `view-users` role for the `realm-management` client. This role is necessary when assigning users to a Customer Portal project.
4750

48-
#### Navigate to Your Customer Portal
49-
1. From the sidebar, go to `Page``Management`
50-
2. Find the `Customer Portal` folder
51-
3. From the `Actions` pull-down menu, go to `View Published Page`
51+
#### D. Navigate to Your Customer Portal
52+
1. From the App Builder sidebar, go to `Page``Management`.
53+
2. Find the `Customer Portal` folder.
54+
3. From the corresponding `Actions` drop-down menu, go to `View Published Page`.
55+
You can set this as your homepage by going to `Page``Settings`, and choosing Customer Portal from the Homepage pull-down options.
5256

5357
![Customer Portal Landing Page](./images/cp-public-landing-page.png)
5458

5559
### Manual Install
56-
1. To install the Customer Portal manually, run the following commands:
60+
1. To install the Customer Portal manually, run the following commands in this order:
5761

5862
``` bash
5963
ent ecr deploy --repo="https://github.com/entando-samples/customerportal-application-bundle.git"
@@ -64,74 +68,72 @@ ent ecr deploy --repo="https://github.com/entando-samples/customerportal-content
6468
```
6569
2. Log in to the App Builder
6670

67-
3. Go to the `Hub` in the left sidebar to view the two Customer Portal bundles. `Install` the `customerportal-application-bundle` first, then the `customerportal-content-bundle`.
71+
3. Go to the `Hub` from the left sidebar. The bundles should be displayed in the Local Hub as `Deployed`. Click the `customerportal-application-bundle` and then `Install`. Repeat for the `customerportal-content-bundle`.
6872

69-
4. To navigate to your Customer Portal:
73+
4. Navigate to your Customer Portal:
7074
1. From the sidebar, go to `Page``Management`
7175
2. Find the `Customer Portal` folder
7276
3. From the `Actions` pull-down menu, go to `View Published Page`
7377

7478
## Configuration
7579
### Administrators
76-
In order to configure the Customer Portal and its users, the administrator needs Jira Service Management and Entando Identity Management System credentials. The admin can then connect the Customer Portal to Jira and customize its features.
80+
To configure the Customer Portal and its users, the administrator needs Jira Service Management and Entando Identity Management System credentials. The admin can then connect the Customer Portal to Jira and customize its features.
7781

78-
>Note: The built-in mapper for email must be enabled on the server client so that user accounts can be retrieved from Jira and new tickets can use that account information.
82+
::: tip
83+
The built-in mapper for email must be enabled on the server client so that user accounts can be retrieved from Jira and service tickets can use that account information.
84+
:::
7985

8086
### Jira Service Management
8187

82-
Users who need access to the Customer Portal, beyond subscription and project information, must have a Jira Service Management account. The administrator utilizes Jira Service Management to create users and projects, define the organization, and configure the service ticket system.
88+
Users who need access to the Customer Portal, beyond subscription and project information, must also have a Jira Service Management account. The administrator utilizes Jira Service Management to create users and projects, define the organization, and configure the service ticket system.
8389

8490
::: tip
85-
The password for Jira Service Management must be an [API token generated by Jira](https://id.atlassian.com/manage-profile/security/api-tokens). For more information, go to [Manange API tokens at Atlassian Support](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
91+
The password for the Ticketing System Connection is requested by the Customer Portal administrator and must be an [API token generated by Jira](https://id.atlassian.com/manage-profile/security/api-tokens). For more information, go to [Manange API tokens at Atlassian Support](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
8692
:::
8793

88-
The JIRA Service Management REST API should follow the pattern https://YOUR-JIRA-SERVICE-MANAGEMENT-URL/rest/api/latest/. For reference, see [Jira Service Management Cloud REST APIs](https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/).
94+
The Jira Service Management REST API should follow the pattern https://YOUR-JIRA-SERVICE-MANAGEMENT-URL/rest/api/latest/. For reference, see [Jira Service Management Cloud REST APIs](https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/).
8995

90-
#### Add Organizations and Projects in Jira:
96+
#### A. Add Organizations and Projects in Jira:
9197
1. Go to Customers
92-
2. Add organizations and projects as needed
98+
2. Add organizations and projects by completing the required fields
9399
3. Click on the name of each added organization to retrieve its ID from the URL. This is required to [create](#create-a-project) and [assign](#assign-a-project) projects in the Customer Portal
94-
- e.g. example.com/jira/servicedesk/projects/ECS/organization/3 → the Organization ID is “3”
100+
- e.g. example.com/jira/servicedesk/projects/ECS/organization/3 → the organization ID is “3”
95101

96102
### Configure the Customer Portal
97103

98104
The Customer Portal must be configured for a specific Jira Service Management instance. The `CP Admin Config` page is where you establish the Jira connection, manage product versions, define subscription levels, and customize ticket types.
99105

100106
To access the `CP Admin Config` page, you must be given the `cp-admin` role in the [Entando Identity Management System](#entando-identity-management-system) as [described above](#assign-roles-to-configure-the-service).
101107

102-
#### View the `CP Admin Config` Page
103-
1. In the App Builder, go to `Pages` and select `Management`
104-
2. Open the Customer Portal folder and find `CP Admin Config`
105-
3. From the `Action` drop-down menu on the right, go to `View Published Page`
108+
#### A. View the `CP Admin Config` Page
109+
1. Go to `Pages` `Management`
110+
2. Expand the Customer Portal folder and find `CP Admin Config`
111+
3. From the corresponding `Action` drop-down, go to `View Published Page`
106112

107113
![Customer Portal Admin Config page](./images/cp-admin.png)
108114

109-
Once the Ticketing System Connection is set up with Jira and the correct URL, default parameters such as product versions and ticket types will be displayed. Open each section with the down arrow to add and edit the fields as needed.
110-
111-
::: tip
112-
The password for the Ticketing System Connection is requested by the Customer Portal administrator and must be an [API token generated by Jira](https://id.atlassian.com/manage-profile/security/api-tokens). For more information, go to [Manange API tokens at Atlassian Support](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
113-
:::
115+
Once the Ticketing System Connection is set up with Jira and the correct URL, default parameters such as product versions and ticket types will be displayed. Expand each section with the down arrow to add and edit the fields as needed.
114116

115117
### Entando Identity Management System
116118
Log in to the Entando Identity Management System to arrive at the landing page shown here. Use the left navigation bar to manage users, groups, and roles. Using the RBAC model, define what access users have by the roles and groups they are assigned. Some important information is noted below.
117119

118120
![Entando Identity Management System](./images/cp-idmanagement-main.png)
119121

120-
#### The Realm Setting
122+
#### A. The Realm Setting
121123
The `Realm` is a set of users, credentials, roles, and groups. A user belongs to and logs in to a `Realm`.
122124

123-
#### Default Roles
125+
#### B. Default Roles
124126
You can use the default roles by clicking on `Client Roles` and choosing `entandodemo-customerportal-server`. Access for each role is defined as follows:
125127

126128
* `cp-customer`: Assigned directly to specific projects of a single customer
127129
* `cp-partner`: Assigned directly to specific projects of multiple customers
128130
* `cp-support`: Read only view of all customer projects
129131
* `cp-admin`: Admin access to the Customer Portal
130132

131-
#### Create New User
133+
#### C. Create New User
132134
1. From the sidebar, go to `Users`
133135
2. Click `Add User` on the right
134-
3. Complete the form as needed, but note the requirements for these fields:
136+
3. Complete the form as needed, but these fields are required:
135137
- `Username`: A unique name
136138
- `Email`: Must use the same address used in Jira
137139
- `User Enabled`: Set to On
@@ -141,16 +143,16 @@ You can use the default roles by clicking on `Client Roles` and choosing `entand
141143
2. Under `Credential Reset`, go to `Reset Actions``Update Password`
142144
3. Click `Send Email`
143145

144-
#### Assign Roles to Users
145-
1. Click on the `Role Mapping` tab
146+
#### D. Assign Roles to Users
147+
1. Click the `Role Mapping` tab on top
146148
2. Select the appropriate role(s) from `Available Roles` and assign them to a user by clicking `Add Selected`:
147149
* To assign default roles, choose `entandodemo-customerportal-server` from the `Client Roles` pull-down
148150
* To manage users in the Customer Portal, a user will need the `view-users` role under `Client Roles``realm-management`
149151
3. Check the `Effective Roles` column on the right to ensure the correct roles have been assigned
150152

151153
![Entando ID Management Role Mapping](./images/cp-identity-userrole.png)
152154

153-
#### Assign Roles to Groups
155+
#### E. Assign Roles to Groups
154156
Under `Groups`, assign roles to groups as needed. Multiple roles can be assigned to a single group.
155157

156158
## Managing the Customer Portal
@@ -159,7 +161,7 @@ As administrator for the Customer Portal, you can create and manage users, custo
159161

160162
![Customer Portal Landing Page](./images/cp-landing-page.png)
161163

162-
#### Create a Customer or Partner
164+
#### A. Create a Customer or Partner
163165
The processes to create customers and partners are similar. Below are the steps to add a `Customer`. A `Partner` is added the same way.
164166
1. Click `Add a Customer`
165167
2. Fill in the customer details. Note:
@@ -168,7 +170,7 @@ The processes to create customers and partners are similar. Below are the steps
168170

169171
![Customer Portal Add Customer](./images/cp-add-customer.png)
170172

171-
#### Create a Project
173+
#### B. Create a Project
172174

173175
1. Go to the Customer Portal landing page
174176
2. Click on a customer to see the associated project list
@@ -177,15 +179,15 @@ The processes to create customers and partners are similar. Below are the steps
177179
5. Provide the [Organization ID](#jira-service-management) retrieved from Jira. Each project must have a unique Organization ID.
178180
6. Click `Save`
179181

180-
#### Assign a Project
182+
#### C. Assign a Project
181183

182184
1. Go to the Customer Portal landing page
183185
2. Click on a customer to see the associated project list
184186
3. From the `Action` drop-down menu, select `Manage Users`
185187
4. Select the user for the `Project`
186188
5. Click `Submit`
187189

188-
#### Manage Partners and Subscriptions
190+
#### D. Manage Partners and Subscriptions
189191
Use the `Action` drop-down menu to manage Partners or request and manage subscriptions.
190192

191193
## Using the Customer Portal

0 commit comments

Comments
 (0)