uses better quality uml diagrams

astitva1905 · Jun 16, 2024 · 2e3cdc0 · 2e3cdc0
1 parent 99e4439
commit 2e3cdc0
Show file tree

Hide file tree

Showing 7 changed files with 3 additions and 3 deletions.
diff --git a/docs/developer/oauth/AUTHMS.md b/docs/developer/oauth/AUTHMS.md
@@ -24,7 +24,7 @@ after user approval.
 Additionally, let's say DTaaS uses a dedicated gitlab instance hosted at the URL
 ”maestro.cps.digit.au.dk” (instead of ”gitlab.com”)
 
-![alt text](oauth2-workflow.jpg)
+![alt text](oauth2-workflow.png)
 
 A successful OAuth2 workflow (Figure 3.3) has the following steps:
 - The user requests a resource, say _GET/BackendMS_

diff --git a/docs/developer/oauth/DESIGN.md b/docs/developer/oauth/DESIGN.md
@@ -45,7 +45,7 @@ of users for any request through the gateway
 The integrated Auth MS should thus work as described in the sequence
 diagram.
 
-![alt text](design-sequence.jpg)
+![alt text](design-sequence.png)
 
 - Any request made by the user is made on the React website, i.e. the
 frontend of the DTaaS software.

diff --git a/docs/developer/oauth/OAUTH2.0.md b/docs/developer/oauth/OAUTH2.0.md
@@ -60,7 +60,7 @@ obtain an access token, using which it can gather user information. Once it
 has user information, it can know the identity of the user and check whether
 the user has permission to access the requested resource.
 
-![alt text](oauth2-workflow.jpg)
+![alt text](oauth2-workflow.png)
 
 The requests made by the Auth MS to the OAuth2 provider
 are abbreviated. A detailed explanation of the workflow for

diff --git a/docs/developer/oauth/design-sequence.jpg b/docs/developer/oauth/design-sequence.jpg
diff --git a/docs/developer/oauth/design-sequence.png b/docs/developer/oauth/design-sequence.png
diff --git a/docs/developer/oauth/oauth2-workflow.jpg b/docs/developer/oauth/oauth2-workflow.jpg
diff --git a/docs/developer/oauth/oauth2-workflow.png b/docs/developer/oauth/oauth2-workflow.png