Applies to: latest versions of the Blackberry and Windows Phone OTP Apps, and for version 4.0.1+ of the SecureAuth App/ Authenticate App for iOS and Android
Introduction:
SecureAuth provides customers an HTML template file to send to end-users to help guide them through the OTP mobile app enrollment process. The template is designed so that the administrator only needs to make two changes to create a customized template for distribution.
Template Customization:
1. Download the latest server-side code (2 files – Redirect.aspx and Redirect.aspx.vb)
2. Remote Desktop into the SecureAuth IdP appliance, and copy the two files toD:\SecureAuth\SecureAuth998
3. Download the latest HTML file, saApp-email-dist-template.zip
4. Open the HTML file with the preferred text editor, such as Notepad or TextEdit
5. Follow the remaining steps to customize the template (optional)
Company Logo
6. To use the company logo, replace the source url in the highlighted section
SecureAuth recommends using a logo no wider than 432 pixels
The image must be hosted on a server accessible from the internet
Launch Button URL
7. In the same HTML file, update the Launch button url by changing the highlighted source to the correct destination users must access in order to register and enroll their device, i.e. change https://youridphost.yourdomain.com to the actual Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance; and change secureauth998 to the correct realm if using a different realm for OATH provisioning
SecureAuth998 is the default OATH Provisioning Realm; however, any realm can be utilized
8. Update the Help Document link (second highlighted section) to include a link to assist users during the process, i.e. replace # with the actual URL
9. Save the file
Send Template as HTML Email
The instructions to send the template as an HTML email depend on the client (browser, mail application, etc.) being used, so please consult its documentation on how to properly send an HTML email
The zip folder that contains the HTML file also contains the images from the template to be utilized as needed on the mail client (uploading, storing, etc.) for the most effective message
NOTE: When uploading the email template on a desktop, be aware that the images and template look different as it was designed for mobile interfaces. When users receive the email on their mobile devices, the format appears as shown in the image above.
Comments
Please sign in to leave a comment.