diff --git a/mbaas/404.html b/mbaas/404.html
index eedb9ee92..c22c87750 100644
--- a/mbaas/404.html
+++ b/mbaas/404.html
@@ -200,7 +200,7 @@
- (C) 2022, Oracle and/or its affiliates
+ (C) 2022, 2023, Oracle and/or its affiliates
diff --git a/mbaas/azure/index.html b/mbaas/azure/index.html
index d70b8e84b..d945eef0d 100644
--- a/mbaas/azure/index.html
+++ b/mbaas/azure/index.html
@@ -65,7 +65,7 @@
"url" : "https://oracle.github.io/microservices-datadriven/mbaas/azure/",
"headline": "Microsoft Azure/OCI Multicloud Installation",
"description": "Microsoft Azure\/OCI Multicloud Installation The Oracle Backend for Parse Platform is available to install in Multicloud (Microsoft Azure and Oracle Cloud Infrastructure (OCI)). This installation deplpoys the Oracle Backend for Parse Platform in Azure with an Oracle Autonomous Database running in OCI.\nPrerequisites You must meet the following prerequisites to use the Oracle Backend for Spring Boot Multicloud (Microsoft Azure and OCI). You need:\nAn account on Microsoft Azure (Azure) An account on OCI Download Download Oracle Backend for Parse Server.",
- "wordCount" : "382",
+ "wordCount" : "384",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
@@ -1427,7 +1427,7 @@
The Authorization Server is an engine to authenticate and authorize requests to various components in Oracle Backend for Spring Boot and Microservices. The end user can manage users using REST Endpoints.
+
+
NOTE: Oracle recommends that you change the default passwords for the default created users.
When deploying Oracle Backend for Spring Boot and Microservices, two users are created with the following roles:
+
+
+
+
User Name
+
Assigned Roles
+
+
+
+
+
obaas-admin
+
ROLE_ADMIN, ROLE_USER
+
+
+
obaas-user
+
ROLE_USER
+
+
+
+
All users are stored in the database are deployed when installing Oracle Backend for Spring Boot and Microservices. The roles determine what the user is allowed to do in the environment. The allowed roles are ROLE_ADMIN and ROLE_USER.
+
+
NOTE: See each components documentation about the roles and authorities.
+
+
The assigned passwords (either auto generated or provided by the installer) can be viewed in the OCI Console (ORM homepage). Click on Application Information.
+
+
+
+
+
+
+
+
+
+
+
+
If you click on Unlock, the password for the obaas-admin and obaas-user can be displayed.
+
+
+
+
+
+
+
+
+
+
+
+
The passwords can also be obtained from k8s secrets using the kubectl command.
In all examples below you need to replace <username>:<password> with your username and password. The examples are using curl to interact with the REST endpoints. They also requires that you have opened a tunnel on port 8080 to either the azn-server or obaas-admin service. For example