3SP Knowledgebase
Information and FAQs about 3SP products
  
Search  
   
Browse by Category
3SP Knowledgebase .: SSL-Explorer .: All Versions .: Web Forwards .: Path-based reverse Proxy .: Domino Web Access

Domino Web Access

Thanks to Tom Sparrow for the following information regarding Domino Web Access and SSL-Explorer


A new webmail redirector (from the Lotus webmailr.ntf template) was created specifically for the SSLExplorer configuration. This was placed in the mail directory on the server along with the mail files (otherwise another path will be required in SSLExplorer).
Note: this is a standard template that is available in Domino - basically it gives a simple URL everyone can use so they don't need to know the specific URL for their personal mailbox.

Open this redirector and click setup. The UI setup and Application Setup are as for our normal (internal) redirector (i.e. follow the instructions, customise as you see fit).

 

Under Server Settings, note the following:

  • Redirector type is Dynamic - this means the server portion of the URL will not be changed from the sslExplorer URL used when the page is opened.
  • Fixed would probably work, but dynamic means you don't have to worry if the SSPExplorer address changes.
  • Leave the path blank
  • Force SSL for the entire session is set to Yes  - otherwise the redirect will revert to http when opening the mailbox, and SSLExplorer won't work.
  • Port number is 443 (standard) unless the SSLExplorer config is non-standard
  • Debug is off.


Create a new Path based reverse proxy in SSLExplorer. The site should be http://server.domain.com/mail/Webmailr.nsf
Add the following paths to the system (explanation in brackets):

  • /mail          *(this is the path to the mailboxes on the server).
  • /iNotes        *(this is an internal DWA address).
  • /icons          (images used by the template - not strictly necessary, but it looks better if it's included).
  • /dwagss.jar    *(a java file used by the iNotes backend. Apparently you can add individual files from the root into the paths and it will work fine).
  • /domcfg.nsf    (this is where the login page is stored. Not actually necessary, but any images on the login page won't appear if it's not there).
  • /NAMES.NSF      (note capitals! - this is where the login page submits to, and you wont get past here unless it's included).


Those with the * are (I imagine) the ones necessary if you only use basic authentication against the domino server.


How helpful was this article to you?

User Comments

Add Comment
No comments have been posted.


powered by Lore
© 2008 3SP Ltd. All Rights Reserved