Authentication to be implemented in REST API in API GW

Hi Experts,

I am using webMethods Api Gateway 10.5. I am in need to create a REST API for which i need to put authentication at API GW layer using user id and password being passed from the source system while calling the API. What should be the policy to be used and how to implement it in API Gateway.

Thanks in advance


You need to configure the “Identify & Authorize Application” under “Identify & Access” stage (Refer the screenshot below). API Gateway supports variety of identification/authentication types like HTTP Basic Authentication, API Key, JWT, Oauth, OpenID etc.

From my understanding of your scenario, you can choose “HTTP Basic Authentication” to authenticate the userid/password from the client. The users need to be already configured in API Gateway or you can authenticate against the LDAP users if you have configured LDAP in the API Gateway.

Based on the “Application Lookup condition” you define, you might need to create an application and define the username in the application and register the application to the API. Request you to go through the documentation if you need more information on “Application Lookup condition”.

Hope this answers your question.



Thanks @Vallab_Chandrasekaran2 for the guidance. So I have selected the HTTP Basic Auth (Registered application) as my current need is to authenticate via user-id and password.

On the other side i have created an application and in the other identifier section is selected username as below:

I have also registered the application in the API. Now while calling and validating from the SOAPUI I am using the

  • Auth header ==> to pass the username
  • Header ==> x-Gateway-APIKey field to pass the API key of the application

Still getting error as below:
[POL:evaluatePolicy]I—> No matching application found for the API : <<service_name>> and Identifier type: token and value Default.

Anything I am missing at my side?


Hi Debapriyo Dasgupta,

What you tried should have worked. Can you please share the product version and the fix level?

Also, please try the scenario without the API Key header (with only Authorization header) and let me know if it works. If it still doesn’t work, please share the screenshot of the application-API association and trace level logs with trace enabled for the below two components.

  1. 0102 IAM (Identity and Access Management)
  2. 0300 Gateway Commons


Hi @Vallab_Chandrasekaran2 ,

So for the version and fix level
Product version :
WmAPIGateway fix : APIGateway_10., APIGateway_10., APIGateway_10.

The API works smoothly when I simply use API Key header (without HTTP Basic auth).

When I changed the Identify & auth policy with only HTTP Basic Auth i am back to the square one. Below are the screenshots

Application Registered

Application details

==== Logs with the suggested trace on =====
logsnippet.txt (12.5 KB)

Let me know what else we can try to achieve the desired outcome.

Also I can see the possibility to put username in application, but what about password as well??

Thanks in advance.


Hi Debapriyo,

Few more questions.

  1. You mentioned 10.5 fix 3, fix 5 and fix 6 as current fix levels. Are these 3 servers clustered or running as stand-alone?

  2. Reg your question below

The application cannot have password. The application is defined for the purpose of identifying a consumer from the request. For example, when you send a request with the “testAdmin” user you mentioned above, API Gateway tries to map this username to identify an application and then check if this application is associated to the API (based on the policy configuration).

However the authentication of the user is done against the API Gateway user management as I already mentioned in my first reply. You need to either define the username/password in API Gateway User Management or you should link LDAP which handles the user authentication.

Please confirm if you have already done the above step.


Hi Vallab,

Ok i got my miss-out. I didn’t create user in the API GW IS :frowning:

Now that i have created a local user with the name testAdmin, this is working fine with userid and password authentication. Even i played around with IP filtering auth option which was also fine.

Thanks a lot for your support. Have a great day.