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: examples/BaSyxSecured/README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,20 +3,33 @@
3
3
All BaSyx components support role-based access control by using Keycloak as identity provider.
4
4
Access rules are defined based on roles. Roles are defined in the Keycloak server.
5
5
6
+
In this setup, an nginx proxy is used to expose the different BaSyx services under dedicated subdomains.
7
+
The main URLs are:
8
+
9
+
AAS Web UI: http://aasgui.basyx.localhost
10
+
11
+
Keycloak: http://keycloak.basyx.localhost
12
+
13
+
Additional service URLs can be found in the docker-compose file.
14
+
15
+
Modern browsers like Google Chrome, Firefox, and others automatically resolve any URL ending with .localhost to the local address 127.0.0.1.
16
+
This means requests to these URLs are directly routed to your own machine, where the nginx instance running inside Docker forwards the requests to the corresponding BaSyx service.
17
+
As an alternative for setups where .localhost handling might not work correctly, you could manually map the required domains to 127.0.0.1 by editing your /etc/hosts file.
18
+
6
19
To start the secure setup execute the following command
7
20
8
21
```bash
9
22
docker-compose up -d
10
23
```
11
24
12
-
This will start the BaSyx components and the Keycloak server. The Keycloak server can be found at http://localhost:9097.
25
+
This will start the BaSyx components and the Keycloak server. The Keycloak server can be found at http://keycloak.basyx.localhost.
13
26
There you can login as admin with username `admin` and password `keycloak-admin`.
14
27

15
28
16
29
The example comes with an already configured realm `BaSyx` and a user `john.doe` with password `johndoe`.
17
30
This user has the `admin` role and can access all BaSyx components and all information about each component.
18
31
19
-
The entry point for accessing the Asset Administration Shells and their Submodels is the AAS Web UI running at http://localhost:3000.
32
+
The entry point for accessing the Asset Administration Shells and their Submodels is the AAS Web UI running at http://aasgui.basyx.localhost.
20
33
After opening the page you will be redirected to the Keycloak login page. Use the credentials of user `john.doe` to log in.
21
34

22
35
@@ -25,7 +38,7 @@ The UI shows the login status in the top right corner.
25
38
To end your session click on the logout button in the top right corner.
26
39

27
40
28
-
There are several other user accounts available, each with different roles. You can use them to test the different levels of access. The password for these users is their username without the dots. You can find them in the [Users](http://localhost:9097/admin/master/console/#/BaSyx/users) tab of the BaSyx realm in Keycloak.
41
+
There are several other user accounts available, each with different roles. You can use them to test the different levels of access. The password for these users is their username without the dots. You can find them in the [Users](http://keycloak.basyx.localhost/admin/master/console/#/BaSyx/users) tab of the BaSyx realm in Keycloak.
29
42
30
43
## Upload AAS Environment files (AASX/JSON/XML) with RBAC
0 commit comments