Configure McAfee Enterprise Security Manager 5.3 as RADIUS client to authenticate to RSA Authentication Manager 8.x
Originally Published: 2016-09-29
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1 and later
Issue
Resolution
Where RADIUS is used to send the authentication to RSA Authentication Manager 8.x deployment, a RADIUS client and an associated RSA agent record must be created using the Security Console for the software/device sending the RADIUS authentication.
- In the Security Console select RADIUS > RADIUS Client > Add New.
- Enter a client name, IP address and IP address.
- Leave the default Make/Model value as - Standard Radius -.
- Create the Shared Secret. This secret must be the same as the one on the RADIUS client.
- Click Save & Create Associated RSA Agent. You will see the message Added 1 RADIUS client(s).
McAfee Enterprise Security Manager requires a RADIUS profile be returned which provides group access after a successful authentication.
- In the Security Console select RADIUS > RADIUS Profiles > Add New.
- Enter a Profile Name.
- In the section for Return List Attributes, select the Filter-ID[M] attribute and enter a value, such as McAfee:version=1:groups=<ACCESS_GROUPS>, replacing <ACCESS_GROUPS> with a comma-separated list of ESM access groups. For example, if you had an ESM access group called AllRights, you would type: McAfee:version=1:groups=AllRights.
- For two access groups called Policy and Reporting that require this policy, you would type McAfee:version=1:groups=Policy,Reporting. For example,
- Click Add in the Return List Attribute section and then click Save.
- Left-click the name of the profile created above.
- Select Associated Users.
- Select Assign to More Users.
- Use the Search Criteria to search for User IDs.
- Select the User IDs to assign to the RADIUS profile and click Assign Profile. For example,
- Perform a RADIUS authentication with the User ID that is assigned the RADIUS profile. In this example a test RADIUS authentication was done using NTRadPing to an RSA Authentication Manager 8.x server.
- In the screen shot we see the RADIUS server reply with an Access-Accept and the Filter-ID and group information crated above.
- The RADIUS log file created in /opt/rsa/am/radius and named for the date that the test was done (in this case, 20160926.log), shows the line:
09/26/2016 15:29:39 Sent accept response for user rsatest to client NTRADPING
- The Authentication Monitor output is as follows:
Notes
Related Articles
RADIUS shared secret limitations of RADIUS clients configured with RSA Authentication Manager 724Number of Views Unable to authenticate to RADIUS server from SonicWALL RADIUS client in RSA Authentication Manager 8.x 518Number of Views Allow a large number of RADIUS clients to authenticate without adding an agent for each client in RSA Authentication Manag… 309Number of Views How to ignore username's NTLM or "down-level logon name" domain name prefix sent by a radius client or agent in RSA Authen… 352Number of Views Adding a Palo Alto RADIUS dictionary to RSA RADIUS for RSA Authentication Manager 8.x 785Number of Views
Trending Articles
RSA Governance & Lifecycle Generic RESTful Web Service Connector Application Guide RSA Release Notes: Cloud Access Service and RSA Authenticators RSA Authentication Manager Upgrade Process RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?