Skip to content

Commit 983e8e2

Browse files
authored
Merge pull request #18365 from jzwickel/master
corrected Issue #18297
2 parents 5380e09 + 52815e9 commit 983e8e2

1 file changed

Lines changed: 6 additions & 10 deletions

File tree

tutorials/hana-cloud-mission-trial-9/hana-cloud-mission-trial-9.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -190,31 +190,27 @@ After you are done, deploy the whole project again. When that is completed succe
190190
191191
Now that you have the role created and granted privileges to this role, it's time to grant this role to a user. We will create the public user `report` that shall have read-only access to the calculation view.
192192
193-
1. Go back to your tab with the **SAP HANA Database Explorer** open or click on the HDI container icon (![Container](icon-container.png)) in the SAP HANA Projects panel.
193+
1. Go back to your tab with the **SAP HANA Database Explorer** and open a SQL Console by clicking on the SQL icon (![SQL](icon-sql.png)) at the top left corner. Make sure that the connection is opened for an user that has system privileges `ROLE ADMIN` and `USER ADMIN`, e.g., database user `DBADMIN`.
194194
195-
2. Open a SQL Console by clicking on the SQL icon (![SQL](icon-sql.png)) at the top left corner.
196-
197-
!![SQL console](ss-06-sql-console.png)
198-
199-
3. Paste the following statement in the SQL Console. Change the password in the statement and then run.
195+
2. Paste the following statement in the SQL Console. Change the password in the statement and then run.
200196
201197
```SQL
202198
CREATE USER report PASSWORD <your_password> NO FORCE_FIRST_PASSWORD_CHANGE set usergroup default;
203199
```
204200

205201
> Using the clause `NO FORCE_FIRST_PASSWORD_CHANGE` is not considered a security best practice! We will only use this option for the purpose of this tutorial, in our example to make a user available to multiple individuals. If you create users in your productive environment, please consider forcing a password change for the first log in and giving individuals different users.
206202

207-
4. Now that our new user `report` is created, we need to grant the user access to the role `PublicAccessSchema`.
203+
3. Now that our new user `report` is created, we need to grant the user access to the role `PublicAccessSchema`.
208204

209-
5. Use the following statement.
205+
4. Use the following statement.
210206

211207
```SQL
212208
GRANT <SCHEMA_NAME>."PublicAccessSchema" to report;
213209
```
214210
215-
6. Replace the `<schema name>` with the calculation view schema you copied in the beginning of this tutorial.
211+
5. Replace the `<schema name>` with the calculation view schema you copied in the beginning of this tutorial.
216212
217-
7. Make sure to remove the `<>` characters and then run the statement.
213+
6. Make sure to remove the `<>` characters and then run the statement.
218214
219215
> ### Custom vs. default roles
220216
>

0 commit comments

Comments
 (0)