Re: Newbie Alert - Dumb Question of the Day!
- From: "callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 20:20:23 -0400
Almost. In WSS 3, you need to let the configuration database (Central
Administration) know that you want the web application to use SSL, then
configure it in IIS.
So you need to go into the Authentication Provider page (off of Application
Management in Central Administration), specify the web application you want
to apply SSL to, and then select to enable SSL.
Remember, all that does is tell sharepoint that the web app will use SSL,
you actually set it up in IIS.
-callahan
"AJ" <andyjones99@xxxxxxxxxxxxx> wrote in message
news:1181588288.676825.306640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 11 Jun, 18:34, "callahan" <cacalla...@xxxxxxxxxxxxxxxxxxx> wrote:
Well AJ, it's like this.
You can have one web application and bunches and bunches of site
collections
in it if you'd like with no problems.
However, a sharepoint web app is an IIS Web Site, and as such is a kind
of
security boundary. You use web applications for applying SSL,
authentication methods, allowing anonymous access (first at the web app,
then it allows you to choose it,individually, at the site
collection/site/list/etc level) to whatever is contain in that web app.
In
addition, you can force security and user account policies at the web
application to all the site collections it contains with policy for web
applications. Also, if you have many, many users, it is sometimes useful
to
split content to two different web applications to lighten the impact of
all
those people accessing the server at once.
There is also something you may not have considered (which is okay, cuz
your
new). Sharepoint can do something called extended web applications.
What
that means it you can create a different web application but have it
access
the same content database as an existing web application. This is good
for
giving two different kinds of users access to the same data from
different
locations like interal network and internet, or for different security
needs, like needing HTTPS outside the office, but using HTTP inside. The
extended web application points to the same data, but will have a
different
web address. Then you can give the users that need more security (maybe
they access the content from the internet) the web address of the web
application that has more security, and give the web application address
of
the non-SSL one to the internal network users.
Does this make any sense at all, or is it a bit to complex for a simple
question? I've been writing my fingers to the bone lately about this
stuff
so it could be too detailed. Sorry about that. ; )
HTH,
-callahan"AJ" <andyjone...@xxxxxxxxxxxxx> wrote in message
news:1181571404.186335.232530@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello All
I am new to SP and WSS3.0 particularly. Can someone tell me when and
why I would need to create a new sharepoint web application? I have
one application created so far and a content database on my SQL 2005
box. From what I can tell I can create as many top level sites and
subsites I like within this web application, so when should I create a
new web sites?
Thanks
AJ- Hide quoted text -
- Show quoted text -
Thanks to the both of you for taking time to respond. Callahan that
was spot on. I use ISA server which helps no end with the SSL stuff
and link translation.
If I wanted to enable SSL on my single sharepoint web app, I am
assuming this is no different from performing this on an IIS website
seeing as this is what it is really?
Thanks again
AJ
.
- References:
- Newbie Alert - Dumb Question of the Day!
- From: AJ
- Re: Newbie Alert - Dumb Question of the Day!
- From: callahan
- Re: Newbie Alert - Dumb Question of the Day!
- From: AJ
- Newbie Alert - Dumb Question of the Day!
- Prev by Date: Re: Error in Application when mail enabling a list
- Next by Date: Re: WSS v3 Directory Management Service
- Previous by thread: Re: Newbie Alert - Dumb Question of the Day!
- Next by thread: Re: Newbie Alert - Dumb Question of the Day!
- Index(es):
Relevant Pages
|
