Commit b9705cd5 authored by Pelayo Torres's avatar Pelayo Torres
Browse files

Update 3 files 

- /doc/images/flows/01_Login_Admin.png
- /doc/testing/postman/README.md
- /doc/images/flows/01_Login Admin.png
parent 229b6e7c

doc/images/flows/01_Login Admin.png

0 → 100644
+28.3 KiB
Loading image diff...

doc/images/flows/01_Login_Admin.png

deleted100644 → 0
−21.9 KiB
Loading image diff...

doc/testing/postman/README.md

+6 −6
Original line number Diff line number Diff line
@@ -77,7 +77,7 @@ Once this is done, the node script will be in charge of changing the certificate 


#### **05-publish_api**



![Flow](../../images/flows/03_AEF_Publish.png)

![Flow](../../images/flows/05_AEF_Publish.png)



Once the api is published, we can start it. In this case we have a test one created in python called <a href="./hello_api.py" download>hello_api.py</a> that can be executed with the following command:
@@ -97,25 +97,25 @@ With this the provider part would be finished. 


#### **07-onboard_invoker**



![Flow](../../images/flows/05_Invoker_Onboarding.png)

![Flow](../../images/flows/07_Invoker_Onboarding.png)



At this point we move on to using certificate authentication in CAPIF. **If you did not configure the provider's certificates, you would have to do it now**.



#### **08-discover**



![Flow](../../images/flows/06_Invoker_Discover_AEF.png)

![Flow](../../images/flows/08_Invoker_Discover_AEF.png)



#### **09-security_context**



![Flow](../../images/flows/07_Invoker_Create_Security_Context.png)

![Flow](../../images/flows/09_Invoker_Create_Security_Context.png)



#### **10-get_token**



![Flow](../../images/flows/08_Invoker_Get_Token.png)

![Flow](../../images/flows/10_Invoker_Get_Token.png)



#### **11-call_service**



![Flow](../../images/flows/09_Invoker_Send_Request_to_AEF_Service_API.png)

![Flow](../../images/flows/11_Invoker_Send_Request_to_AEF_Service_API.png)



With this, we would have made the API call and finished the flow.