If you are new to DualShield, then you might want to first refer to the general instruction on how to build an application in DualShield.
Complete the following steps to build an application for Outlook Anywhere
Create logon procedure for Outlook Anywhere
Before an application can be created, a logon procedure must be created first.
In the Admin Console, in the side panel, select "Authentication | Logon Procedure"
Click the "CREATE" button on the toolbar
In the "Name" field, enter a name for this new logon procedure, e.g. "Office 365"
In the "Type" field, select the type of the logon procedure from the drop list, e.g. "Web SSO"
Click the "SAVE" button to save it.
Now that a new logon procedure is created, you want to add logon steps.
To add logon steps to a logon procedure or to change logon steps, firstly navigate to the logon procedure.
Navigate to Authentication | Logon Procedures
Click the context menu icon "..." of the application to be edited, e.g. "Office 365"
select "Logon Steps" to bring up the logon steps editor
To add a logon step, click the "ADD" button
Select the one or multiple authentication methods that you want to add to this step, e.g. "One-Time Password"
Click the "SAVE" button to save it
You can change the order of the steps by clicking the "UP" and "DOWN" buttons.
If you are implementing the device-based Outlook Anywhere MFA, then
For Outlook Anywhere Device-Based Authentication, you must create a logon procedure in the type of Exchange Mail.
Once a logon procedure has been created, you need to add logon steps into the newly created logon procedure.
For Outlook Anywhere Device-Based Authentication, you only need to add one logon step and within the logon step you can only add "Computer DeviceID" as the authentication method.
If you are implementing the agent-based Outlook Anywhere MFA, then
For Outlook Anywhere Agent-Based Authentication, you must create a logon procedure in the type of Web SSO.
Once a logon procedure has been created, you need to add logon steps into the newly created logon procedure.
For Outlook Anywhere Device-Based Authentication, you can add multiple logon steps if you wish. Typically, you would only need to add one logon step. Within the logon step, you can add any authentication method such as One-Time Password
If you are implementing both the agent-based and device-based Outlook Anywhere MFA, then you must create both the logon procedures as above.
Create application for Outlook Anywhere
In DualShield, an application does not have a type. Therefore, creating an application for any integration is the same.
In the Admin Console, in the side panel, select "Authentication | Applications"
Select "CREATE" on the toolbar
Select the Realm to be linked to this application, e.g. Deep.Net
Select the Logon Procedure to be used by this application, e.g.. Office 365
If you are implementing the Device-Base Outlook Anywhere MFA, then you must select the Logon Procedure that is of the type of Exchange Mails, e.g. "Outlook Anywhere Device-Based" that was created in the previous step
Agent-Base Outlook Anywhere MFA
If you are implementing the Agent-Base Outlook Anywhere MFA, then you must select the Logon Procedure that is of the type of Web SSO, e.g. "Outlook Anywhere Agent-Based" that was created in the previous step
Both Device-Based & Agent-Base Outlook Anywhere MFA
If you are implementing both the Agent-Base and Device Based Outlook Anywhere MFA, then you must select both Logon Procedures
Publish application for Outlook Anywhere
Generally, an application has to be published before it can be accessible by users.
To publish an application on an authentication agent, first navigate to the application list by selecting "Authentication | Applications" in the side panel
Click the context menu icon "..." of the application, e.g. "Office 365" to access its context menu
select "Agents" in the context menu
select the authentication agent on which the application is to be published, e.g. "Single-Sign-on Server"
Click "SAVE" button to save the settings
The Outlook Anywhere application has to be published on one or many Single Sign-On (SSO) servers.
You might see two SSO servers in your DualShield platform, one called "SSO Server" and the other called "Single Sign-on Server". The so-called "SSO Server" is the legacy SSO server in DualShield 5 and the "Single Sign-on Server" is the new SSO server in DualShield 6.