Mirket OWA Agent
The first steps are to prepare the installation files on the server where Exchange is located.
Then, the IIS Manager is opened. The Default and Backend are stopped.
For using multi-factor authentication in Outlook Web Access (OWA) accesses, the following steps need to be performed within the Exchange server:
Then copy everything except Bin folder into C:\Program Files\Microsoft\ExchangeServer\V15\ClientAccess\Owa. These folders depicted in Figure 2.25 will be provided to the individual responsible for the installation by the Mirket Support team.
Then copy MultiFactor.IIS.Adapter.dll and Newtonsoft.Json.dll files in Bin folder to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\Bin directory.
The web.config file inside the C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa directory is opened.
· The Multifactor module is added within the modules tag, as seen below:
<modules runAllManagedModulesForAllRequests="false">
--> <add type="MultiFactor.IIS.Adapter.Owa.Module, MultiFactor.IIS.Adapter" name="MFA" />
</modules>
· Two keys are added within the appsettings tag.
* mirket:api-url => Mirket URL related.
* mirket:disaster-scenario-bypass => In a disaster scenario, it checks whether a bypass should occur when Mirket cannot be reached (true, false). False is recommended if provider is Approve/Deny.
<appSettings>
--> <add key="mirket:api-url" value="https://10.10.10.212" />
--> <add key="mirket:disaster-scenario-bypass" value="false" />
</appSettings>
After the above changes are made, start the OWA backend and frontend via IIS.
If you wish to disable Mirket on OWA, the following steps should be taken.
· The following line added to the modules tag is commented out (<!-- comment line -->) or removed. Afterward, the OWA application (Figure 2.26) is restarted via IIS.
<modules runAllManagedModulesForAllRequests="false">
--> <!-- <add type="MultiFactor.IIS.Adapter.Owa.Module, MultiFactor.IIS.Adapter" name="MFA" /> -->
</modules>
Related Topics
Last updated