minor change, rename files

Fraunhofer-IESE · Jan 10, 2024 · e814422 · e814422
1 parent 1383c98
commit e814422
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 2 deletions.
diff --git a/...sm - OAuth2 - Authorization Code Flow.svg → ...anagement/Consent Flows/SVG/Auth-Code.svg b/...sm - OAuth2 - Authorization Code Flow.svg → ...anagement/Consent Flows/SVG/Auth-Code.svg
diff --git a/...sm - OAuth2 - Client Credentials Flow.svg → ...gement/Consent Flows/SVG/Client-Creds.svg b/...sm - OAuth2 - Client Credentials Flow.svg → ...gement/Consent Flows/SVG/Client-Creds.svg
diff --git a/...re Document/Quality Concepts/Security/Consent Management/Consent Flows/index.md b/...re Document/Quality Concepts/Security/Consent Management/Consent Flows/index.md
@@ -5,6 +5,6 @@ The following diagrams illustrate the two supported flows for obtaining consents
 1. Diagram 1 illustrates the consent flow using OAuth2 Authorization Code Flow. The expected interaction between our demo  _KST Basic FMIS_ system and our _KST Platform_  is depicted. _KST Basic FMIS_ a single page application (SPA) that supports the farmer in managing the fields of his/her farm. The data used by  _KST Basic FMIS_  is stored in our  _KST platform_.
 2. Diagram 2 illustrates the consent flow using OAuth2 Client Credentials Flow. The expected interaction between our demo  _Agricultural Service Provider_ system and our _KST Platform_  is depicted.
 
-![Diagram 1 - OAuth2 - Authorization Code Flow](SVG/KST-%20Consent%20Mechanism%20-%20OAuth2%20-%20Authorization%20Code%20Flow.svg)
+![Diagram 1 - OAuth2 - Authorization Code Flow](SVG/Auth-Code.svg)
 
-![Diagram 2 - OAuth2 - Client Credentials Flow](SVG/KST-%20Consent%20Mechanism%20-%20OAuth2%20-%20Client%20Credentials%20Flow.svg)
+![Diagram 2 - OAuth2 - Client Credentials Flow](SVG/Client-Creds.svg)