Radius assertion errors - No credentials were found

Document ID : KB000118466
Last Modified Date : 25/10/2018
Show Technical Document Details
Question:
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 Doc 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] Wiki page
"https://docops.ca.com/ca-api-gateway/9-2/en/policy-assertions/assertion-palette/access-control-assertions/authenticate-against-radius-server-assertion/"

[2] Require XPath Credentials
https://docops.ca.com/ca-api-gateway/9-2/en/policy-assertions/assertion-palette/access-control-assertions/require-xpath-credentials-assertion/
Environment:
ENV: 9.3
Answer:
The attached sample policy that authenticates users with credentials specified in an HTML form. A policy author will only need to change the "Set Context Variable" assertions 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. 

 
File Attachments:
requireHtmlFormCredentials.xml