Advertisement

06.11.2008 at 03:50PM PDT, ID: 23477729
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

Sharepoint SSL and IIS

Asked by bden219606 in MOSS-Sharepoint, Microsoft IIS Web Server, Secure Socket Layer (SSL) & HTTPS

Tags: , ,

We have a single webserver running multiple websites that need to use SSL (some integrated, some FBA). We are using currently using host header names to accomodate for this but this could clearly be not the best solution. SP likes to use **UnAssigned**, from what I've read and tried, and the wildcard SSL certificates are not working too well.

With SSL, host headers cant be used since the header is inside of the encrypted packet. This means each website would need to have its own Private IP Address AND its own public IP Address. Currently were basically out of public IPs. Using a VIP on the firewall wont work because a VIP maps one public IP to many private IPs depending on the port. Having to remember which port each website is on isnt user friendly at all! We own a wildcard certificate but its not supported with Sharepoint. Weve tried many workarounds so far be they didnt work.

any ideas?Start Free Trial
[+][-]06.11.2008 at 08:51PM PDT, ID: 21766096

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]06.12.2008 at 11:05AM PDT, ID: 21772082

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]06.18.2008 at 04:12PM PDT, ID: 21818064

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: MOSS-Sharepoint, Microsoft IIS Web Server, Secure Socket Layer (SSL) & HTTPS
Tags: Microsoft, Sharepoint, 3.0, 2007
Sign Up Now!
Solution Provided By: bden219606
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628