From afa58388c3c3084edaf15bd61890b715d93a9344 Mon Sep 17 00:00:00 2001
From: Kostis Trantzas <ktrantzas@ece.upatras.gr>
Date: Tue, 8 Apr 2025 14:29:03 +0300
Subject: [PATCH] Fix for clarifying the need for a user with username "admin"
 (#19)

---
 doc/getting_started/deployment/docker_compose.md | 3 +++
 doc/getting_started/deployment/kubernetes.md     | 6 +++++-
 mkdocs.yml                                       | 2 +-
 3 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/doc/getting_started/deployment/docker_compose.md b/doc/getting_started/deployment/docker_compose.md
index 31ef05f7..c4f609ef 100644
--- a/doc/getting_started/deployment/docker_compose.md
+++ b/doc/getting_started/deployment/docker_compose.md
@@ -457,11 +457,14 @@ Finally, enter the details of the mail server at the Email Tab.
 This step is mandatory so as to access the OpenSlice Web UI. To add an OpenSlice admin user you must:
 
 - Navigate to realm Openslice > Users > Add user
+- Set ```admin``` username
 - Set a password
 - Upon creation, navigate to Role Mappings and add ADMIN to Assigned Roles list
 
 > That user is different from the Keycloak admin user. It is required to login and browse the OpenSlice Web UI. The Role ADMIN guarantee full access through the OpenSlice UI, thus such a user is always required.
 
+> You may have multiple ADMIN role users, but you must have at least one with ```admin``` username.
+
 ### Keycloak at localhost
 
 > **This is an important step if you run Keycloak on localhost!**
diff --git a/doc/getting_started/deployment/kubernetes.md b/doc/getting_started/deployment/kubernetes.md
index a3f794ed..8776f280 100644
--- a/doc/getting_started/deployment/kubernetes.md
+++ b/doc/getting_started/deployment/kubernetes.md
@@ -516,12 +516,16 @@ Finally, enter the details of the mail server at the Email Tab.
 #### 2. Add an OpenSlice admin user
 
 This step is mandatory so as to access the OpenSlice Web UI. To add an OpenSlice admin user you must:
-- Navigate to realm Openslice > Users > Add user 
+
+- Navigate to realm Openslice > Users > Add user
+- Set ```admin``` username
 - Set a password
 - Upon creation, navigate to Role Mappings and add ADMIN to Assigned Roles list
 
 > That user is different from the Keycloak admin user. It is required to login and browse the OpenSlice Web UI. The Role ADMIN guarantee full access through the OpenSlice UI, thus such a user is always required.
 
+> You may have multiple ADMIN role users, but you must have at least one with ```admin``` username.
+
 ### NFV Orchestrator Configuration
 
 After successfully deploying and configuring OpenSlice, you may configure its environment (e.g. the NFVO) that will facilitate the deployment of NFV artifacts.
diff --git a/mkdocs.yml b/mkdocs.yml
index 34924275..c5d95f3c 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -167,7 +167,7 @@ nav:
       - Jenkins Helm Installation aaS : ./service_design/examples/jenkins_helm_install_aas/jenkins_helm_install_aas.md
       - Monitoring aaS: ./service_design/examples/monitoring_aas/monitoring_aas.md
   - Service Ordering:
-    - Ordering Services from catalogs: ./service_ordering/ordering_services.md
+    - Ordering Services from Catalogs: ./service_ordering/ordering_services.md
   # - Testing services:
   #   - Testing Specification: ./testing_services/test_spec.md
   #   - Testing Catalogs: ./testing_services/test_catalogs.md
-- 
GitLab