Securing APIs with Mutual SSL¶
In contrast to the usual one-way SSL authentication where a client verifies the identity of the server, in mutual SSL the server validates the identity of the client so that both parties trust each other. This builds a system that has a very tight security and avoids any requests made to the client to provide the username/password, as long as the server is aware of the certificates that belong to the client.
This section explains how to APIs in WSO2 API Manager can be secured using mutual SSL in addition to OAuth2.
- Create an API Secured with Mutual SSL
- Invoke an API Secured with Mutual SSL from the Developer Portal
Create an API Secured with Mutual SSL¶
- Create an API .
- Navigate to the Runtime Configurations tab.
Select Mutual SSL.
Click Upload Certificate to upload a new client certificate.
This feature currently supports only the
.crtformat for certificates.
If you need to use a certificate in any other format, you can convert it using a standard tool before uploading.
Provide an alias and public certificate. Select the tier that should be used to throttle out the calls using this particular client certificate and click Upload .
Save the API
Invoke an API secured with Mutual SSL using Postman¶
Import the certificte and private key to Postman. Navigate to certificates tab in Postman settings.
Add the certificate and private key.
Invoke the API from Postman.
Listed below are the known limitations for this feature.
Application subscription is not permitted for APIs that are only protected with mutual SSL. Hence, subscription/application level throttling is not applicable for these type of APIs.
Resource level throttling is not applicable for the APIs that are only protected with mutual SSL.
Resource level security will not be applicable for the APIs that are only protected with mutual SSL.
Scope level security will not be applicable for the APIs that are only protected with mutual SSL.