Windows MFA Agent - Auth Manager Integration

[NicanorPulido]

Hi team,

with the MFA Windows Agent, it is not clear to me what is the value that should be used in the "Agent Name" attribute. It is clear that it must be the same value that is created as an Agent in the AM Security Console, but, in a massive deployment, how can it be automated?

With the traditional agent, there is an autoregistration option, in which the Agent "enrolls" with the server, but I cannot find any similar option with the MFA agent.

Many thanks for your clarification.

[RobertG]

Hello NicanorPulido,

For REST protocol authentication agents, which the MFA Agent is one, a single authentication agent record can represent multiple machines that have the agent installed. So you can have the agent installed on multiple machines, use the same authentication agent name for each one, and configure just one authentication agent in the Security Console with the same name.

[RussCSwartz]

When configuring that authentication agent record on the Security Console, what do you do about the IP addresses. Do you add one for each of the servers with the same name? Or is this part of the process automated? 

[RobertG]

Russ,

The only field that you need to define in the Authentication Agent record for the MFA Agent for Windows is the "hostname" field. You can leave the IP Address field blank. For this record for the MFA Agent, the hostname field does not have to be set to a "real" hostname: it just needs to match up with the Authentication Agent name set in the GPO settings for the agent.