E-Pass Installation Questionnaire
| 1) Which E-Pass modules will you be utilizing(Check all that apply)? Metering Day Pass E-Wallet Term Subscriptions |
| 2) Will users be required to register before viewing metered content? Yes No |
| 3) Will social network login and registration be used? Yes No |
| 4) If answering Yes to number 3, which social networks (check all that apply)? |
| 5) How many publications will be protected (editions)? Edition Codes: |
| 6) If metering, how many page views before forcing login or registration? This is the number pages a user can view before being denied access to content and
forced to buy a subscription. |
| 7) If metering, and not forcing registration, how many days before a user can start viewing metered content again? When registration is not forced,
a cookie is set to count page views. Likewise, another cookie is set to clear the counter for page views so users can again view protected content until the limit is reached
again.
|
| 8) What should the default length of the password be (characters)? |
| 9) When users are authenticated, their login information is stored on the computer. This prevents users from having to enter this information on a
page by page or day basis. This login information can be set to expire based on the
subscription end date or a specific number of days, which will force the user to re-enter their login information after that time. Do you want to use the subscription end date
as the cookie expiration date? Yes No |
| 10) If no to the question above, what should the default number of days for the cookie login information expiration be? |
| 11) When users are authenticated, a cookie is set that will automatically grant access to content. This is done to prevent unnecessary traffic from
the content server to the Newzware server with every page view. For example: A user purchases a term subscription and logs in and is granted access.
The user then cancels their subscription, but has already logged in and has been granted access, so there is no authentication attempt.
Since they have canceled and a cookie is already set with an authenticated value, re-authentication
is then necessary to get back the most recent information, preventing the user to be given access to other protected content.
Re-authentication is automatically set in the E-Pass module and re-sends any login information.
The default is every 15 minutes. This can be set to a shorter duration or longer duration. If you want something other than the default, please specify in
minutes the desired amount of time between re-authentication attempts? |
| 12) When users are prompted to purchase a Term, Day Pass or E-Wallet subscription, a default can be set to automatically show one of the subscription types.
If you desire a default type be opened, specify which here. The default is each option is closed until the user selects one. |
| 13) The E-Pass module prevents two users from using the same login at the same time. If this is detected, the module presents the user to log into their
account (SSM) to log off any sessions. The E-Pass module can be set to automatically log the user into the SSM or force them to enter the login and password into the SSM's
login page. The default behavior is to force the user to login into the SSM, causing more frustration for the user sharing logins.
Specify your default behavior. Yes, automatically log them in. No, force them to enter credentials again. |
| 14) For E-Wallet subscriptions, specify the credit blocks that you want to offer, such as, 5,10,20,50,100 dollars. |
| 15) For E-Pass to work, there are two methods that can be employed to display content. 1) Place the protected content into a div element and set the display attribute to none. Give that div element an id and set the nwContentId in the E-Pass configuration file to that id. When a user is authenticated, that element will be displayed. This method is not 100% foolproof in its protection of your content, since the content is already loaded in the page and can be seen in the document's view source. This is the most common option if no Javascript expertise is on site. 2) Set the nwContentCallback variable to a call back method in your own javascript that will load and display the contents. This can be any method name, but must be defined in the document. An example of this is as follows: nwContentCallback="displayContent()" . Once the user is authenticated, the displayContent() javascript method is called. The displayContent() method would then load the protected content via AJAX and place it correctly in the document. This method is 100% secure, as the protected content is only loaded into the document upon a successful authentication. The drawback to this method is it requires some technical expertise to write the javascript function. Enter the method that the site will be using. Div element id show Javascript call back method |