Skip to content

Commit a632825

Browse files
authored
Makes DynamicRBAC image references relative
1 parent 5149bfe commit a632825

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

examples/BaSyxDynamicRBAC/README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
* The administrator of the system controls the policy/access rules inside the Submodel.
55
* Rules can be added or deleted during the system's runtime.
66

7-
<img width="60%" alt="image" src="images/DynamicRBACMgmt.png">
7+
<img width="60%" alt="image" src="./images/DynamicRBACMgmt.png">
88

99
## Prerequisites
1010
1. REST API Client (e.g., [Postman](https://www.postman.com/downloads/))
@@ -20,15 +20,15 @@ docker-compose up -d
2020
This will start the BaSyx components and the Keycloak server. The Keycloak server can be found at http://localhost:9097.
2121
There you can login as admin with username `admin` and password `keycloak-admin`.
2222

23-
<img width="60%" alt="image" src="images/users.png">
23+
<img width="60%" alt="image" src="./images/users.png">
2424

2525
The example comes with an already configured realm `BaSyx` and a user `john.doe` with password `johndoe`.
2626
This user has the `admin` role and can access all BaSyx components and all information about each component.
2727

2828
The entry point for accessing the Asset Administration Shells and their Submodels is the AAS Web UI running at http://localhost:3000.
2929
After opening the page you will be redirected to the Keycloak login page. Use the credentials of user `john.doe` to log in.
3030

31-
<img width="60%" alt="image" src="images/login.png">
31+
<img width="60%" alt="image" src="./images/login.png">
3232

3333
## Security in BaSyx
3434

@@ -112,7 +112,7 @@ Following shows how a JSON based RBAC rule looks like a Submodel-based rule:
112112
| ManufacturerFrame | dave | dave |
113113
| ManufacturerGear | dave | dave |
114114

115-
<img width="60%" alt="image" src="images/AASDS2.png">
115+
<img width="60%" alt="image" src="./images/AASDS2.png">
116116

117117
### View Rules for this example
118118

@@ -139,7 +139,7 @@ Similarly, you can create idShorts using the below TargetInformation class as pe
139139

140140
### Scenario
141141

142-
<img width="80%" alt="image" src="images/BicycleExampleDataspaceFlow_short.png">
142+
<img width="80%" alt="image" src="./images/BicycleExampleDataspaceFlow_short.png">
143143

144144
* When Frame Supplier delivers the product they also add a policy/rule (using Dynamic RBAC) so that the manufacturer can see the Digital Twin of the supplied product.
145145
- Postman -> AASDataspace -> Rules -> Frame (In Postman collection)
@@ -178,4 +178,4 @@ Similarly, you can create idShorts using the below TargetInformation class as pe
178178
- Postman -> AASDataspace -> Rules -> Manufacturer
179179
- Go to GET_GearAAS request or GET_SupplierSMFrom_GearAAS -> Authorization -> Get New Access Token (at very bottom) -> Use Token
180180
- Send the request
181-
- These requests will return 200 OK
181+
- These requests will return 200 OK

0 commit comments

Comments
 (0)