cancel
Showing results for 
Search instead for 
Did you mean: 

OWA/Archive Explorer/SSL in EV 8 SP3

evinfo
Level 4

Hello -

I have 2 questions regarding OWA/ArchiveExplorer/SSL.

1. Currently when we are testing our external OWA, archive explorer keeps going to "http://" rather than "https://". Can someone tell me what we need to change for Exchange 2007 and EV8 SP3/IIS 6? When we chose port "443" on the "web application" on the site configuration, nothing seemed to be happening.

2. Also, we do not want our users to acess archive explorer directly externaly (eg. "https://owa.companyname.com/enterprisevault/archiveexplorer.ui") though when the user clicks on "ArchiveExplorer" button in OWA it goes that exact website. So basically we don't want to publish that website directly to the client (how can we go about doing that?). We don't mind user going to that website once they have been 2-factor authenticated (with RSA) into OWA and then click on "ArchiveExplorer" and go to the website, as our security team has all sorts of issue with users going directly to the archiveexplorer website without "2-factor" authentication. Hope I'm clear on that.

I would appreciate any thoughts or direct me to any published documents on this subject, as there are not any clear OWA documents published which makes it straight forward.


2 REPLIES 2

MichelZ
Level 6
Partner Accredited Certified
1. Port 443 should be suffice, I believe. You need to Synchronize the mailboxes that it takes effect.
2. That's probably something your reverse proxy should take care about...

cloudficient - EV Migration, creators of EVComplete.

evinfo
Level 4
Michael - thank you very much I was able to switch over the port 443.

My question regarding "Hiding archiving explorer" ev address "https://owa.companyname.com/enterprisevault/archiveexplorer.ui" when a user clicks on "Archiveexplorer" through OWA. Does EV alway try to connect directly to the EV server for "ArchiveExplorer" and "Search"?

And if so, to hide the address so that it's not exposed to the user, are you recommending that we work with our IIS resources to configure a ReverseProxy solution which hides the real address and also so that we do not have to open up the archive explorer site.

Any help is appreciated.