Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Metering
  5. General and security settings
  6. Permissions
  7. Schedules
  8. Bundle management
  9. Event monitoring
  10. Troubleshooting security
  11. Licenses

Organization Administration

Organization Administration

Fingerprint authentication properties

Fingerprint authentication properties

You can enforce a fingerprint authentication every time the Secure Agent starts. An authentication failure can trigger an email alert but allow normal operations, or it can disallow agent startup.
To set the authentication mode, configure the options in
Fingerprint Authentication
on the
Organization
page.
You can configure these levels of authentication enforcement:
No enforcement, no notifications
Disable fingerprint enforcement and don't specify an email address.
No authentication check is performed when the Secure Agent starts up. This is the default.
Report violations only
Disable fingerprint enforcement and specify an email address. The email format is checked, but the validity of the email address isn't verified. Be sure to allow emails from the address "admin@informaticacloud.com".
An authentication check is performed during Secure Agent start up. Any fingerprint mismatch triggers a notification to the email recipient, but the agent starts up normally.
Enforce authentication match
Set fingerprint enforcement to
On
and specify an email address. The email format is checked, but the validity of the email address isn't verified. Be sure to allow emails from the address "admin@informaticacloud.com".
Any fingerprint mismatch triggers a notification to the email recipient and the Secure Agent log in is prevented from starting up.
An email address is required if enforcement is turned on.
A fingerprint is created the first time a Secure Agent starts up, using device attributes from the agent's host machine. The data is anonymized and hashed to produce a unique fingerprint. When switching from no enforcement to any other level of enforcement, the Secure Agent generates a fingerprint the first time it starts up.
If you reinstall the Secure Agent on the same machine, the fingerprint doesn't change.
The following table summarizes what happens when fingerprint enforcement prevents the Secure Agent from starting up:
Action
Message
Error is logged to agentcore.log
"Internal error. Agent <Secure Agent ID> fingerprint is not matching with the previous stored value for request <Request ID>."
Email notification is sent (if an email address was specified)
"There was a fingerprint mismatch while logging in agent with name <Secure Agent name> for Organization <Organization ID>. The agent was last active on <Date in UTC>."

0 COMMENTS

We’d like to hear from you!