Allowing parallel access - https and http

[Matt Kale]

Is there any reason (other than security) why we should not allow both http
and https traffic to PWA?

It's a long story, but anyone who can get to that server is a trusted user
and it's not available over the internet - but for certain known reasons
normal HTTP links do not work with PWA for remote (WAN) users. We have
enabled SSL access, and those links work fine.

Is there anything within the application or database that might cause us
problems down the line? We have it up and running fine in a development
environment and I can't find any adverse affects... Links to WSS work fine,
MS Project Pro works fine, etc. If we change the server to only allow HTTPS
traffic - all sorts of functionality breaks.

Thanks in advance.

 

[Earl Lewis]

Matt,

We're using SSL exclusively and nothing seems to be broken for us. What exactly is breaking on you?

I hope I don't need to say this but if you're passing logins over an unencrypted channel they can be sniffed and if those logins provide access to sensitive company information, well... you know the rest.

Earl
Is there any reason (other than security) why we should not allow both http
and https traffic to PWA?

It's a long story, but anyone who can get to that server is a trusted user
and it's not available over the internet - but for certain known reasons
normal HTTP links do not work with PWA for remote (WAN) users. We have
enabled SSL access, and those links work fine.

Is there anything within the application or database that might cause us
problems down the line? We have it up and running fine in a development
environment and I can't find any adverse affects... Links to WSS work fine,
MS Project Pro works fine, etc. If we change the server to only allow HTTPS
traffic - all sorts of functionality breaks.

Thanks in advance.

 

[Matt Kale]

We were never able to get SSL working for both PWA and WSS. 4 days on the
phone with Microsoft left me with nothing but a complete re-install.
You know the Admin page Manage Windows SharePoint Services where you change
the URLs to HTTPS, etc for Central Admin and Create Sites Under, etc...?
Well no matter what we tried we could never get it to update to https. Long
story, don't really want to re-hash. Suffice to say we have an apparently
operational work-around. Before I implement in our production environment
I'm just trying to get a 'sanity check' there isn't something that will cause
us problems down the road.

re: Clear text - yes I'm aware. All the users access the site securely.
Some of the WAN users come in via Firewall to Firewall VPN which is as
securely encrypted as it can be. The problem is the Firewall's don't like
some of the URLs that Project Server generates - they are self-referencing
and appear to be Trojan-like behavior. Generating these URLs is supposed to
be against Microsoft SOP, but go figure. By changing the links to HTTPs we
avoid the issues with the firewalls.

Thanks for the reply. If anyone has any tips or pointers, please let me know!