Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
Authenticating webMethods.io API Gateway APIs using OAuth2.0 using a local authorization server
This article explains about how to implement OAuth 2.0 on API Gateway for local authorization server
It is assumed that readers of this article know how to set up API’s and policies on API Gateway.
• Active tenant subscription on webMethods.io API Gateway • Configure the API at API gateway. • Create Application and associate API with the application. • Refer the link to create API GitHub - SoftwareAG/webmethods-api-gateway: Repository hosting developer tutorials, code samples, custom policies, CI/CD scripts and more to enable developers develop faster with API Gateway
• We configured the API on API Gateway. This API checks the availability of beds in hospitals. • To invoke this API from API Gateway we have implemented the OAuth 2.0 mechanism. • In our case our API Gateway will be working as an authorization server. • First we will get the access token from the authorization server and then the same token will be passed to access the API.
OAuth 2.0 is the industry-standard protocol for authorization. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices.
For detailed information follow the below link: OAuth 2.0 — OAuth
**API Name:** CheckBedAvailability
Add Scope to Auth Server
Access Token: https://<>.apigw-aw-us.webmethodscloud.io/invoke/pub.apigateway.oauth2/getAccessToken Grant Type: Client Credentials Client ID: Available in the application Client Secret: Available in the application Client Authentication: Send As Basic Auth header