filmov
tv
RAML Design With Anypoint Platform - Part III | MuleSoft | Security Scheme
Показать описание
This is third video in the series which will talk about how to design APIs using RAML.
There will be demonstration on designing APIs using basic RAML. Here we will see how to implement custom security schemes.
- Build and Design Security Schemes in RAML
Each authentication pattern supported by the API must be expressed as an element of the Security Schemes node value. The Security Schemes should be created under a separate folder and included within the API RAML file.
Supported Security Schemes are defined below.
OAuth 1.0: API authentication requires using OAuth 1.0
OAuth 2.0: API authentication requires using OAuth 2.0
Basic authentication: API authentication relies on using basic authentication, and will need to pass username and password checks.
Digest authentication: API authentication relies on using digest authentication.
Pass-through: Headers or query parameters are passed through to the API based on a defined mapping.
x-{other}: API authentication relies on another authentication mechanism. You can define custom Security Schemes prefixed with “x-”. Please refer to the below example for custom Security Schemes.
It is very important to design the APIs before actual implementation and get feedback from users, developers or stakeholder.
Here is some blogs provides more information on RAML
There will be demonstration on designing APIs using basic RAML. Here we will see how to implement custom security schemes.
- Build and Design Security Schemes in RAML
Each authentication pattern supported by the API must be expressed as an element of the Security Schemes node value. The Security Schemes should be created under a separate folder and included within the API RAML file.
Supported Security Schemes are defined below.
OAuth 1.0: API authentication requires using OAuth 1.0
OAuth 2.0: API authentication requires using OAuth 2.0
Basic authentication: API authentication relies on using basic authentication, and will need to pass username and password checks.
Digest authentication: API authentication relies on using digest authentication.
Pass-through: Headers or query parameters are passed through to the API based on a defined mapping.
x-{other}: API authentication relies on another authentication mechanism. You can define custom Security Schemes prefixed with “x-”. Please refer to the below example for custom Security Schemes.
It is very important to design the APIs before actual implementation and get feedback from users, developers or stakeholder.
Here is some blogs provides more information on RAML
Комментарии