---
title: SecTrail MFA Integration
slug: singleconnect-reference-guide-3-1-0/sectrail-mfa-integration
description: Learn how to seamlessly integrate Single Connect with SecTrail in this comprehensive document. Discover the requirements, including the use of Active Directory or Single Connect Local accounts and the necessity of mobile phone numbers in user accounts. Ga
docTags: 
createdAt: 2022-07-31T18:30:23.000Z
---

To integrate Single Connect with SecTrail, users must:

-
  Use Active Directory or Single Connect Local accounts.
-
  Have mobile phone numbers in their accounts defined in Active Directory.


Single Connect operates between Active Directory and SecTrail.


Single Connect integrates with SecTrail via API, provided certain parameters are defined in Single Connect:

-
  API key (the API key is created by SecTrail for each customer environment)
-
  Token Generate URL (OTP Messaging URL)
-
  Token Validation URL (OTP Validation URL)


To adjust the SecTrail Integration Settings:

1. Navigate to** Administration **> **System Config Manager**.
2. Set the following parameters:                                                                                                            mfa.provider=sectrail (default: internal)
   mfa.external.provider.sectrail.apiUser=XXX (encrypted)
   mfa.external.provider.sectrail.apiKey=XXX (encrypted)
   mfa.external.provider.sectrail.generateTokenUrl=\*
   (For example: [https://1.2.3.4/externalwebservice](https://1.2.3.4/externalwebservice))
   mfa.external.provider.sectrail.otpValidUrl=\*\*
   (For Example: [https://1.2.3.4/externalwebservice](https://1.2.3.4/externalwebservice))
   mfa.external.provider.sectrail.httpHeaders=
   (default=“**Content-Type\:application/json**” - Common header definition for both URLs)
   (Value can be parsed with enter for more than one header attribute)