--- sourceDocument: Brazil Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # Set up time-limited authentication with SMS - Twilio tutorial # Set up time-limited authentication with SMS - Twilio tutorial {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Set up time-limited authentication with MFA factors such as SMS using Twilio. ## Before you begin Role required: adaptive_auth_admin, user_admin Plugins required: * com.snc.authenticate.time_limited_authentication (Time Limited Authentication) * com.snc.authentication.sms_mfa (Multi-factor authentication with SMS) {#time-based-authentication-with-mfa__ul_egd_4jr_jvb} Note: Time limited authentication (TLA) is very specific to ServiceNow instance. The customized links for users can only be created within ServiceNow. The tutorial instructions provided enable the admin to provide a link-based login with SMS as second factor (MFA) for users with a specific role. After a successful configuration, the system generates a link, and then shares the link with the user through notification (Email/SMS) channel. Selecting the link, the user is prompted to specify the OTP sent to Email or SMS factor based on user role (configuration). Note: * TLA should be followed by MFA and MFA should be enabled by admin using Adaptive Authentication for TLA login. To learn more about how to configure MFA with Adaptive Authentication, see [Multi-factor Authentication context](https://www.servicenow.com/docs/vYirFCwtH5voBqWWW2e4Gg "The Multi-factor Authentication (MFA) policy context uses a policy to define how and when MFA is enforced during the login process."). * TLA should be used for the users who have limited privileges. {#time-based-authentication-with-mfa__ul_cwv_c24_fwb} ## Procedure 1. Create a Twilio configuration. 1. Create a Twilio test account. For more information, see [Twilio](https://www.twilio.com/login). 2. Navigate to AllNotifyAdministrationTwilio Direct Configuration. 3. Provide the Account SID and Auth token (created from Twilio) and save the record. {#time-based-authentication-with-mfa__substeps_jwl_4hm_fwb} Note: You can create your own provider configuration and use that for TLA. In this example, it is Twilio. To learn more about how to create an MFA provider configuration, see [Configure MFA Provider](https://www.servicenow.com/docs/UFw8dUQn8ZAXv9ke0JusBw "Configure SMS and Email with the Provider to ensure every user can login securely."). 2. Configure and enable Time limited authentication (TLA) record. 1. Navigate to AllTime Limited Authentication Config records and select New. 2. On the form, fill in the fields. {#time-based-authentication-with-mfa__table_mxz_wyp_znb__entry__2} | Field | Description | |-|-| | Name | Name of the record. | | One time use | Option to use the TLA link once. | | Expiry | Number of seconds for the link expiry. The default is 45 minutes. | | Failed Redirect | URL to redirect users after a failed authentication. | | Single Sign-On Script | Details of the SSO script to use. | | Active | Option to make the configuration active. | | Max login attempts | Number of attempts allowed with the generated TLA link for login. Clear the One time use check box to provide the max number of attempts. | | External logout redirect | URL to redirect users after logout. | [Table 1. Time Limited Authentication form] {#time-based-authentication-with-mfa__table_mxz_wyp_znb} 3. Select Submit. 4. Navigate to AllMulti-Provider SSOAdministrationProperties and enable the Enable multiple provider SSO property and Save. {#time-based-authentication-with-mfa__substeps_dhr_1mg_fwb} 3. Allow TLA to only a specific user persona using the post-authentication context policy. 1. Navigate to Roles and create a role. For example: remote_worker. 2. Create a user with a valid email id and mobile number. To learn how to create a user, see [Create a user](https://www.servicenow.com/docs/access?context=t_CreateAUser&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). 3. Assign the role to the user. To learn how to assign the role to the user, see [Assign a role to a user](https://www.servicenow.com/docs/access?context=t_AssignARoleToAUser&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). 4. To create a role filter criteria, navigate to AllAdaptive AuthenticationRole Filter Criteria, create a new filter remoteworkerrole and condition Role is remote_worker. 5. To add policy condition based on the deny policy context based on the IdP and role filter criteria, navigate to AllAdaptive AuthenticationPost Authentication Context. 6. Select the information icon and Open the Record. 7. In the Policy Input, select Edit and add the role (remoteworkerrole) and Save. 8. In the Policy Condition, add the condition for the policy input and Submit the record. {#time-based-authentication-with-mfa__substeps_alk_fng_fwb} 4. Configure the step-up authentication policy - MFA context. 1. Navigate to AllMulti-factor Criteria. 2. Select the Role based multi-factor authentication and add the role under Multi-factor Roles section and Update. In this example: remote_worker. 3. Navigate to AllAdaptive AuthenticationMFA Context. 4. Make sure the following: * Default Policy field is Step-up MFA Policy * Step-Up MFA Policy is Step-up MFA Policy {#time-based-authentication-with-mfa__ul_gv3_nkj_kvb} 5. Select the information icon and Open Record. 6. On the Step-Up MFA Policy form, in the Policy Inputs, select Edit. 7. Add the Role based multi-factor authentication to the list and Save. In this example, remoteworkerrole. 8. In the Policy Condition, select Enforce MFA if Role based or User based MFA settings are true. 9. In the Enforce MFA if Role based or User based MFA settings are true page, make sure Role Based MFA is true. {#time-based-authentication-with-mfa__substeps_d1h_pyn_fwb} 5. Enforce MFA to use SMS as an MFA factor policy. 1. Navigate to AllAdaptive AuthenticationMFA Context. 2. On MFA Context page, select MFA Factor Policies and select the policy Display SMS OTP as an MFA Factor Policy. 3. Select Edit and add remoteworkerrole in the Policy Inputs. 4. Select Policy Conditions and create a Policy condition. 5. Select Submit. The TLA link generated and shared to the users assigned with remoteworkerrole as role will be promoted to use the SMS code as a second factor to login the instance. {#time-based-authentication-with-mfa__substeps_etl_pyn_fwb} 6. Enable the other required properties. 1. Navigate to AllMulti-factor AuthenticationProperties. 2. Select the following check boxes. * Enable Multi-factor authentication * Enable Multi-factor Authentication with SSO {#time-based-authentication-with-mfa__ul_k1p_2lr_jvb} 3. Save the record. 4. Navigate to AllAdaptive AuthenticationAuthentication PoliciesProperties. 5. Select the Enable Authentication Policy check box. 6. Save the record. {#time-based-authentication-with-mfa__substeps_w2y_4mg_fwb} 7. Generate a TLA link -- Example. 1. Navigate to AllSystem DefinitionScripts -- Background. 2. Use the following API by providing user sys_id and config id. `var tla=new global.TimeLimitedAuthentication(); gs.info(tla.generateNonce("user_sysid", "config1_sys_id","IAR2"));` Note: The source (IAR2) is not a required parameter. 3. Query Parameter is returned as shown: `nonce=VCeinfboDt0M&glide_sso_id=b3277f1b44351110f8779b5a2d9909f3&user=3b0277d344351110f8779b5a2d99099a&source=IAR2` 4. Create a URL in the following format: `https:// /login_with_sso.do?uri=& nonce=2olIQSxdgkjs&glide_sso_id=0c15bf09c3711110c5ec4e483c40dd7a&user=62826bf03710200044e0bfc8bcbe5df1&source=IAR  ` {#time-based-authentication-with-mfa__substeps_e5g_cmg_fwb} 8. Select the URL, the following MFA screen is displayed for login. *[\>]: and then