Re: Using SecureSocketsLayer rather than None
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Feb 2006 22:57:54 -0600
Adding SecureSocketsLayer with no port specified will switch to the default
SSL/LDAP port, 636.
To answer the first question, you are probably safe on the same box. But,
if you are using SSL in IIS and are using the same DNS name for ADAM as IIS,
why not just use the IIS SSL cert and be thorough?
Joe K.
"sl" <connect@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23EmY06vNGHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
Oh and as a follow up.
If i use AuthenticationTypes.SecureSocketsLayer but do not use the SSL
port in my connection path (or vice versa) will it default to forcing an
SSL connection (i'm putting aside some time to test this later).
thanks,
steven :: http://stevenR2.com
"sl" <connect@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OZoNKovNGHA.1716@xxxxxxxxxxxxxxxxxxxxxxx
When AD/AM is running on the same server as IIS (and the application) how
necessary is it that the bind goes over SSL?
I would almost always say it should always be over SSL, but i have read
in a few places that it is not a huge requirement when on the same box.
thanks,
steven :: http://stevenR2.com
.
- References:
- Prev by Date: Re: A weird error in event viewer
- Next by Date: Re: ADAM Bind to alias pointing local server fails
- Previous by thread: Re: Using SecureSocketsLayer rather than None
- Next by thread: testing all replication
- Index(es):
Relevant Pages
|
