Knowledge Base

Support Policies

SecureAuth 2nd Factor OTP Formatting Requirements and Best Practices

SecureAuth IdP Version affectedAll

 

Description:
This document describes the formatting best practices for phone numbers and email addresses when the utilizing second factor options in SecureAuth.

Discussion:

International Numbers

When formatting international numbers SecureAuth requires the string to start with a country code followed by a space. A country code starts with a plus (+) symbol followed by the country code. For example if you wanted to enter the SecureAuth sales phone number it would be +1 949 777 6959 . The remainder of the numbers in the dial string can use any combination of the following separators 'space', 'dash' or 'period'. You can also choose to forgo the use of separators in your number string (ex. +1 9497776959).

National Numbers

A national number can use any combination of the following separators 'space', 'dash' or 'period'. You can also choose to forgo the use of separators in your number string (ex. 9497776959).

E-Mail Addresses

An email address should follow the format local-part@domain where the local-part may be up to 64 characters long and the domain name may have a maximum of 255 characters as defined in RFC 5322 (sections 3.2.3 and 3.4.1).

Best Practices

SecureAuth recommends formatting phone numbers and email addresses per the International Telecommunication Union E.123: Notation for National and International Telephone numbers, e-mail addresses and web addresses specification. This internationally accepted standard will help ensure interoperability with telephone and email systems worldwide. Below please find examples of a national number, international number and email address in the E.123 format.

National (042) 123 4567
International +31 42 123 4567
   

ITU E.164 Support

SecureAuth supports the ITU E.164 Format for international phone numbers.



Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.