You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: vuepress/docs/next/tutorials/solution/customer-portal.md
+48-46Lines changed: 48 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ sidebarDepth: 2
4
4
5
5
# Entando Customer Portal
6
6
## 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.
8
8
9
9
Key Features:
10
10
@@ -28,32 +28,36 @@ This tutorial covers:
28
28
29
29
### Automatic Install via the Entando Hub
30
30
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:
34
34
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`
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.
40
44
41
-
#### Assign Roles to Configure the Service
45
+
#### C. Assign Roles to Configure the Service
42
46
1.[Log in to your Keycloak instance](../../docs/consume/identity-management.md#logging-into-your-keycloak-instance) as an admin
43
47
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.)
46
49
- Assign the user the `view-users` role for the `realm-management` client. This role is necessary when assigning users to a Customer Portal project.
47
50
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.
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:
57
61
58
62
```bash
59
63
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
64
68
```
65
69
2. Log in to the App Builder
66
70
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`.
68
72
69
-
4.To navigate to your Customer Portal:
73
+
4.Navigate to your Customer Portal:
70
74
1. From the sidebar, go to `Page` → `Management`
71
75
2. Find the `Customer Portal` folder
72
76
3. From the `Actions` pull-down menu, go to `View Published Page`
73
77
74
78
## Configuration
75
79
### 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.
77
81
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
+
:::
79
85
80
86
### Jira Service Management
81
87
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.
83
89
84
90
::: 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/).
86
92
:::
87
93
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/).
89
95
90
-
#### Add Organizations and Projects in Jira:
96
+
#### A. Add Organizations and Projects in Jira:
91
97
1. Go to Customers
92
-
2. Add organizations and projects as needed
98
+
2. Add organizations and projects by completing the required fields
93
99
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”
95
101
96
102
### Configure the Customer Portal
97
103
98
104
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.
99
105
100
106
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).
101
107
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`
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.
114
116
115
117
### Entando Identity Management System
116
118
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.
The `Realm` is a set of users, credentials, roles, and groups. A user belongs to and logs in to a `Realm`.
122
124
123
-
#### Default Roles
125
+
#### B. Default Roles
124
126
You can use the default roles by clicking on `Client Roles` and choosing `entandodemo-customerportal-server`. Access for each role is defined as follows:
125
127
126
128
*`cp-customer`: Assigned directly to specific projects of a single customer
127
129
*`cp-partner`: Assigned directly to specific projects of multiple customers
128
130
*`cp-support`: Read only view of all customer projects
129
131
*`cp-admin`: Admin access to the Customer Portal
130
132
131
-
#### Create New User
133
+
#### C. Create New User
132
134
1. From the sidebar, go to `Users`
133
135
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:
135
137
-`Username`: A unique name
136
138
-`Email`: Must use the same address used in Jira
137
139
-`User Enabled`: Set to On
@@ -141,16 +143,16 @@ You can use the default roles by clicking on `Client Roles` and choosing `entand
141
143
2. Under `Credential Reset`, go to `Reset Actions` → `Update Password`
142
144
3. Click `Send Email`
143
145
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
146
148
2. Select the appropriate role(s) from `Available Roles` and assign them to a user by clicking `Add Selected`:
147
149
* To assign default roles, choose `entandodemo-customerportal-server` from the `Client Roles` pull-down
148
150
* To manage users in the Customer Portal, a user will need the `view-users` role under `Client Roles` → `realm-management`
149
151
3. Check the `Effective Roles` column on the right to ensure the correct roles have been assigned
150
152
151
153

152
154
153
-
#### Assign Roles to Groups
155
+
#### E. Assign Roles to Groups
154
156
Under `Groups`, assign roles to groups as needed. Multiple roles can be assigned to a single group.
155
157
156
158
## Managing the Customer Portal
@@ -159,7 +161,7 @@ As administrator for the Customer Portal, you can create and manage users, custo
0 commit comments