Image fix and readme postman

## CAPIF Flows

Once the first steps have been taken, we can now use Postman requests. These requests are numbered in the order that must be followed to obtain everything necessary from CAPIF.

### Creation of an user

### Creation of User by Admin

The first step would be for an administrator to create a user with which a provider and an invoker will be created.

The first step would be for an administrator to create a user with which a provider and an invoker will be created. To do this, the admin must log in to obtain the token needed in admin requests.

#### **01-Login_admin**

![Flow](../../images/flows/01_Login_Admin.png)

#### **02-Register of User**

#### **02-Creation of User**

![Flow](../../images/flows/02_Register_of_User.png)

![Flow](../../images/flows/02_Creation_of_user.png)

### Publication of an API

The next step is to register a provider using the user created by the administrator in order to publish an API.

#### **03-getauth_provider**

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

#### **04-onboard_provider**

![Flow](../../images/flows/02_AEF_API_Provider_registration.png)

![Flow](../../images/flows/04_AEF_API_Provider_registration.png)

At this point we move on to using certificate authentication in CAPIF. In Postman it is necessary to add the certificates manually and using more than one certificate for the same host as we do in CAPIF complicates things. For this reason, we use the script to overwrite a certificate and a key when it is necessary to have a specific one.

### Calling the API

Finally, we will create an invoker with the user given by the administrator to be able to use the published api.

#### **06-getauth_invoker**

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