NSD1168 How to Install One Time Password Server Prefetch ASP.NET Web
Application on IIS 6
Fact
Nordic Edge One Time Password Server, IIS 6, Prefetch ASP.NET Web Application
Situation
Installing the One Time Password Prefetch ASP.NET Web Application
Solution
The OTP prefetch application ships with two pages (two different scenarios).
● Self Service - SelfService.aspx is a self service page. The user logs in and gets a number of prefetch passwords by SMS or e-mail.
● Centralized Administration - CentralizedAdmin.aspx is a centralized administration page. An "OTP prefetch password"-administrator logs in and gets a number of prefetch passwords, for a selected user account, by e-mail.
System Requirements
● Nordic Edge One Time Password Server 1.6 or later ● Microsoft .NET Framework 2.0 or later
● IIS 6
Prerequisites
● Nordic Edge One Time Password Server installed and configured to use SMS or e-mail to send OTP
Installation
● Download the OtpPreFetch.zip
● In Internet Information Services (IIS) Manager: Click New > Virtual Directory...
● Enter an Alias ● Click Next >
● Enter your application path (the directory where OtpPreFetch.zip was unzipped) ● Click Next >
● Mark Read, Run scripts (such as ASP) and Execute (such as ISAPI applications or CGI) ● Click Next >
● Click Finish
● Now, right-click the OtpPreFetch Virtual Directory in the IIS Manager and choose Properties ● Change the ASP.NET version to 2.0.x
● Click OK
● Browse to the application (http://localhost/OtpPreFetch/SelfService.aspx) and verify that the Web Application is working as expected
Figure: The SelfService.aspx Page
Configuration
Open ~/wwwroot/OtpPreFetch/bin/web.config with an editor like Notepad.exe. In the section <appSettings> you’ll find the host tag.
The tag <system.web> provides language and culture support.
<configuration> <appSettings>
<add key="host" value="127.0.0.1:3100"/> </appSettings>
<connectionStrings/> <system.web>
<!-- <globalization enableClientBasedCulture="true" culture="Auto" uiCulture="Auto"/> --> <!-- NOTE: If Culture is set "Auto", Culture is set by the browser -->
<!--globalization enableClientBasedCulture="true" culture="sv-SE" uiCulture="sv-SE"/--> <globalization enableClientBasedCulture="true" culture="en-US" uiCulture="en-US"/>
● Change, if necessary, the “host” value for your environment.
● To change the language support to swedish, uncomment the following row:
<globalization enableClientBasedCulture="true" culture="sv-SE" uiCulture="sv-SE"/>
Comment out the row for english language support:
<!--globalization enableClientBasedCulture="true" culture="en-US" uiCulture="en-US"/-->
Modify Content in SelfService.aspx or CentralizedAdmin.aspx
● If you want to change the default value (5) in “Numbers of…” to, for instance 10, make these changes:
<asp:ListItem>5</asp:ListItem><asp:ListItem Selected="True">10</asp:ListItem>
…and to add another digit
<asp:ListItem>25</asp:ListItem> <asp:ListItem>35</asp:ListItem> <asp:ListItem>50</asp:ListItem>
● If you want to add an item or a method, in this case “chatAttribute” and Chat, to the “Send via” drop down list, just add the tags below:
margin-top: 6px;">
<asp:ListItem Value="mobile">SMS</asp:ListItem> <asp:ListItem Value="mail">e-Mail</asp:ListItem>
<asp:ListItem Value="chatAttribute">Chat</asp:ListItem> </asp:DropDownList>
Configuration for Centralized Administration Page
The CentralizedAdmin.aspx works as the SelfService.aspx except from some differences. These are: ● The account which generates the prefetch passwords has to be an "OTP prefetch administrator" ● The Help Desk may want to receive the generated OTP's instead of the user receiving the OTP's
● How to configure an "OTP prefetch administrator" in the OTP Server, see NSD1183
● How to configure the OTP Server to send an e-mail containing prefetched OTP's to a static "OTP prefetch receiver", see NSD1184
One Time Password Server Configuration
Now, you have to add your IIS Web Server as a client in your One Time Password Server configuration. How to add a client is described in the One Time Password Server 3.0 – Administrators Manual in section 13 Client Configuration.
Revision History
Version/Date Note Version 1.6.1 11th januari 2011Installation guide now describes adding the application to an existing IIS web site (instead of creating a new IIS web site)
Version 1.6
30th December 2010
● Added Default.aspx ● Added language support
● Renamed Login.aspx to SelfService.aspx ● Renamed LoginAdmin.aspx to
CentralizedAdmin.aspx