The CA SSO (SiteMinder) Policy Servers can act as both a RADIUS Server or as a RADIUS client or as both RADIUS Server and RADIUS client simultaneously.
As a RADIUS Server, the Policy Server accepts RADIUS protocol requests from external RADIUS clients, typically network access servers (NAS), and returns RADIUS protocol responses. As a RADIUS Server, the Policy Server can only perform Authentication, return RADIUS responses and acknowledge client RADIUS accounting requests. As a RADIUS Server, the Policy Server does not perform authorization except what is implicit in the type and values of the RADIUS responses returned.
As a RADIUS client, the Policy Server accepts user credentials and makes an authentication request using the RADIUS protocol to a external RADIUS Server. The RADIUS Server performs authentication and returns a RADIUS response such as RADIUS Accept or Reject. In this RADIUS client configuration, the Policy Server delegates the test of credentials portion of authentication to the configured RADIUS Server and uses the RADIUS Server response type--Accept or Reject--to determine if the user credentials are valid. The Policy Server ignores any RADIUS response attributes returned in the RADIUS Server's response. After a successful RADIUS authentication, the Policy Server will search for the user in the configured User Directories and, if found, will perform the remaining Policy Server authentication process and create a typical "SiteMinder" user "session" based on the user identity and directory. This requires the user login name or identity to be found in a configured Policy Server User Directory but the Policy Server will not check the password against that directory. If the request to the Policy Server was an Agent API Login request from a Web Agent, the Agent can build an SMSESSION cookie from the Policy Server response. Once the session exists, the Policy Server can complete typical authorization.
Your questions suggest that you want the Policy Server to act as RADIUS client and authenticate against an external RADIUS server. To configure this for basic user name and password, configure a realm with the RADIUS Server Authentication Scheme. In that scheme, configure the IP address, port and secret for the RADIUS Server. This scheme accepts username and password and will produce a Basic challenge (HTTP 401 challenge) in a browser. This authentication scheme does not work with an HTML form.
The XAUTH RADIUS Solution Module may be required if you need forms-based RADIUS authentication. XAUTH RADIUS integration with the Policy Server may provide additional capabilities as well.