Showing posts with label ssl. Show all posts
Showing posts with label ssl. Show all posts

Sunday, 19 February 2012

Confirming encryption when Replication is over SSL

We are using SSL to secure merge replication from client to server. Though
we can check through network monitor whether data is encrypted for normal
query to database, for replication how can we confirm that data is
encrypted - as data is already being send in binary format.
Could you please let me know how to check if data is encrypted when we do
replication over SSL.
Thanks,
Ganesh.Same process Ganesh. Run one of the Agents in Replication such as the
Distribution Agent and verify that the data being sent is encrypted using a
network sniffer or Microsoft Network Monitor. Running SQL Profiler will
show the data un-encrypted.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin.
Ganesh.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:c4bYLAiLEHA.2364@.cpmsftngxa10.phx.gbl...
> Same process Ganesh. Run one of the Agents in Replication such as the
> Distribution Agent and verify that the data being sent is encrypted using
a
> network sniffer or Microsoft Network Monitor. Running SQL Profiler will
> show the data un-encrypted.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Friday, 17 February 2012

Configuring SQL Reporting Services for SSL

I've got an issue that is perhaps a bit different than any other
related posting on this topic.
I have successfully installed and configured SSRS for SQL 2005 and now
I'm at the step where I need to require SSL. So I opened the
Reporting Services Configuration, then selected Report Server Virtual
Directory. Then I select the checkbox Require Secure Socket Layer
(SSL) connections. At this step I am required to enter the name of
the certificate. Here is the problem: The server in on 2 seemingly
different domains and the certificate was issued to domain A, but the
server name is listed under domain B, but both domains resolve to the
same IP address. Here are the specifics:
A) The cert was named according to this domain pattern:
<server_name>.orgA.domainA.com
B) The computer name in system properties is:
<server_name>.orgB.xx.domainB.com
When I run the report server web interface, I get this error "The
request failed with HTTP status 401: Unauthorized."
So my question is: Why isn't the certificate for Domain A working?
Should I request a certificate under the domain of option B above? Is
there a configuration that is required? Note - I've modified the file
rsreportserver.config per the installation instructions.
Thanks in advance for your assistance,
-ScottOn Mar 6, 10:33 am, scottdistef...@.gmail.com wrote:
> I've got an issue that is perhaps a bit different than any other
> related posting on this topic.
> I have successfully installed and configured SSRS for SQL 2005 and now
> I'm at the step where I need to require SSL. So I opened the
> Reporting Services Configuration, then selected Report Server Virtual
> Directory. Then I select the checkbox Require Secure Socket Layer
> (SSL) connections. At this step I am required to enter the name of
> the certificate. Here is the problem: The server in on 2 seemingly
> different domains and the certificate was issued to domain A, but the
> server name is listed under domain B, but both domains resolve to the
> same IP address. Here are the specifics:
> A) The cert was named according to this domain pattern:
> <server_name>.orgA.domainA.com
> B) The computer name in system properties is:
> <server_name>.orgB.xx.domainB.com
> When I run the report server web interface, I get this error "The
> request failed with HTTP status 401: Unauthorized."
> So my question is: Why isn't the certificate for Domain A working?
> Should I request a certificate under the domain of option B above? Is
> there a configuration that is required? Note - I've modified the file
> rsreportserver.config per the installation instructions.
> Thanks in advance for your assistance,
> -Scott
Anybody thoughts?|||On Mar 6, 11:33 am, scottdistef...@.gmail.com wrote:
> I've got an issue that is perhaps a bit different than any other
> related posting on this topic.
> I have successfully installed and configured SSRS for SQL 2005 and now
> I'm at the step where I need to require SSL. So I opened the
> Reporting Services Configuration, then selected Report Server Virtual
> Directory. Then I select the checkbox Require Secure Socket Layer
> (SSL) connections. At this step I am required to enter the name of
> the certificate. Here is the problem: The server in on 2 seemingly
> different domains and the certificate was issued to domain A, but the
> server name is listed under domain B, but both domains resolve to the
> same IP address. Here are the specifics:
> A) The cert was named according to this domain pattern:
> <server_name>.orgA.domainA.com
> B) The computer name in system properties is:
> <server_name>.orgB.xx.domainB.com
> When I run the report server web interface, I get this error "The
> request failed with HTTP status 401: Unauthorized."
> So my question is: Why isn't the certificate for Domain A working?
> Should I request a certificate under the domain of option B above? Is
> there a configuration that is required? Note - I've modified the file
> rsreportserver.config per the installation instructions.
> Thanks in advance for your assistance,
> -Scott
I'm sorry to pester, but I'm running out of things to try on this
issue. Does anyone have thoughts to share on requiring SSL with SQL
2005 Reporting?

Friday, 10 February 2012

Configure SSL after installing SQL Server 2000 Reporting Services?

How do you configure SRS to use SSL after you've installed it?First you must configure IIS with a certificate. Once that is done you need
to determine the level of SSL that you want RS to be configured for. You
can find out information for that here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_soapapi_dev_2xiq.asp
Once you pick a level, just set the SecureConnectionLevel element in the
RSReportServer.config file and you should be up and running.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrik Ylén" <PatrikYln@.discussions.microsoft.com> wrote in message
news:2BFBCC2F-7115-4F9B-ACF4-7FB90E0D1B03@.microsoft.com...
> How do you configure SRS to use SSL after you've installed it?