Radius assertion errors - No credentials were found

Products

• CA API Gateway

Issue/Introduction

The user needs to do Radius authentication from a custom HTTP header transferring the username and password. They are able to use the example from the document page [1] using Basic Authentication. However, the user needs to extract the credentials from a custom HTTP header. When trying to use "Require XPath Credentials" [2], the Radius assertion logs that "No credentials were found" although the "Require XPath Credentials" assertion passed with the given input.

How can we pass custom string values as username/password values to the Radius assertion?

[1] Authenticate Against Radius Server Assertion
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/11-0/policy-assertions/assertion-palette/access-control-assertions/authenticate-against-radius-server-assertion.html

[2] Require XPath Credentials Assertion
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/11-0/policy-assertions/assertion-palette/access-control-assertions/require-xpath-credentials-assertion.html

Resolution

The attached sample policy helps to authenticate the user with credentials specified in the HTML form. A policy author will only need to change the "Set Context Variable" assertion to reflect the name of the HTML form fields that contain the username and password. 

The policy can be simplified to only use the "Require XPath Credentials" assertion to point to the variable that refers to the HTML form fields but the policy provided simplifies the process.