The Securities RAML Fragment project aims to streamline the development of RAML (RESTful API Modeling Language) specifications by adhering to predefined standards for security schemas. It provides a set of reusable fragments focused on security, enabling the creation of consistent and standardized RAML specifications for APIs.
The project encompasses 7 distinct security schemas, each serving a specific purpose in securing your APIs:
-
clientEnforcement: Standard client enforcement security schema.
-
basicAuthentication: Basic authentication security schema.
-
digestAuthentication: Digest authentication security schema.
-
oAuth1.0: OAuth 1.0 authentication security schema.
-
oAuth2.0: OAuth 2.0 authentication security schema.
-
passThrough: Pass-through security schema.
-
anotherAuthentication: Custom security schema tailored for specific requirements.
The anotherAuthentication
security schema stands out as a customized solution, while the others are predefined by RAML. This diversity allows you to choose and implement the most suitable security measures for your API.
The Securities RAML Fragment project facilitates the integration of various security schemas into your RAML specifications, promoting a secure and standardized approach to API development.
- Create a new RAML Fragment project in Design Centre named: "Securities RAML Fragments"
- Add all the contents of this repository into a ZIP excluding the license and readme.md file.
- Ensure you set the root RAML as the one which has been imported.
- Publish this asset to Exchange.
- This asset can now be imported into any new API Specification Design Centre project.
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Distributed under the MIT License. See LICENSE.txt
for more information.
Used as the basis for creating this template.
- reusable-raml-fragments
- 3 types of API fragments design strategies
- RAML Version 1.0: RESTful API Modeling Language