Configure back-end authentication for an API
2 minute read
Before you start
- You will need a user account for AMPLIFY Central
- You will need an API which supports back-end authentication
Learn how to configure authentication for your back-end API.
Add back-end HTTP basic authentication to an API proxy
The following procedure demonstrates how to configure HTTP basic back-end authentication for a sample API, and how to deploy and test the API.
Import an API with HTTP basic authentication as an API proxy
Select API Proxies in the left navigation bar, click Register API, and import an API that supports HTTP basic authentication.
This example uses a sample musical instruments API. You can import this from: https://39cd48c2323117d7f0ec53a347aa94d8974a2174.cloudapp-enterprise.appcelerator.com/apidoc/swagger.json
Configure HTTP basic back-end authentication for the API proxy
On the Policies tab, change the back-end authentication policy to
HTTP Basic Auth and enter the authentication credentials. The credentials can be a user name and password combination or only a user name with no password.
The credentials for the sample musical instruments API are:
- user name/password:
- user name/no password:
Watch the animation to learn how to do this in AMPLIFY Central UI.
Changing the back-end authentication policy (for example, from no authentication to HTTP basic authentication) always creates a new revision of the API proxy.
Deploy and test the API proxy revision
On the Deployments tab, deploy or update a runtime group with this revision of your API proxy.
On the Test Methods tab, execute a method. It should return a
200 OK result. This indicates a successful call of the API using HTTP basic as the back-end authentication.
If you execute a method and it returns a
401 Unauthorized result, this indicates an unsuccessful call of the API (for example, due to invalid authentication credentials).
Update HTTP basic authentication credentials
You can update the HTTP basic authentication credentials after deploying the API proxy. The backend authentication dialog displays the previously set credentials, but as password is a secure field, it is not revealed.
Changing the HTTP basic authentication credentials for a deployed proxy revision creates a new revision of the API proxy. If the proxy revision is not deployed, the current revision is updated.
You have learned how to configure back-end authentication for your API in AMPLIFY Central.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.