Authentication across internet

From what I have understood, Reporting Services could be configured to use Basic Authentication. In this way, a user can access a RS-server across the internet and he/she will be prompted for a valid username/password when trying to access.

However, from what I can understand this username and password will be sent uncrypted over the Internet (from the client machine to the RS-server), right?

My problem is, I need to give access to users acress the internet to a RS-server. The users uses all kind of operating systems (Windows, Linux, MacOS tec). And the communication needs to be encrypted.

How would you recommend me to implement security for this solution? I guess some kind of "Forms authentication" will have to be used? But how to make sure the data traffic is encrypted? And where do you recommend me to store the username and passwords? In an Active Directory on the server side, or in a separate database on the server side?

regards Andreas

You need to set up your report server to use SSL, that way all communication is encrypted. This would be done in IIS but also requires some config chages to reporting services.

Both Basic authentication and Forms would work in this scenario.

Use AD for the user accounts if possible.

|||

Thank you for your quick reply!
My SSL experience is very limited as well, but I guess it means that I need to buy a certificate from some trusted store? Otherwise the clients will always be warned when trying to connect, right?

Regards Andreas

|||If you have a fix client list, give them a link to download your own CA public key should be good enough. Of coz if its facing internet I suggest you pay for SSL. Not only your authentication, your report data are flying nude via the line, I guess that might be another issue and reason why SSL is required.|||

Ok, thank you for your answers! An SSL-certificate it will be!

Just so that I didn't missunderstood. If I configure IIS to use SSL, the login name and password will be safly encrypted, even if I use Basic authentication, or?

Regards Andreas

|||Yes, ALL communication is encrypted.sql

Attempt to fetch logical page error

Hello,
I have recently moved some packages I had been working on from my development to production environment. Having come across many configuration related errors, I believed my latest one to be of this type. However I'm recieving one I've never seen before:

"Attempt to fetch logical page (1:95152) in database 8 failed. It belongs to allocation unit 72057594043301888 not to 72057594045661184.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly"

This package works fine on the development db, however I don't even know where to start tracking this issue down. Any thoughts?

Thanks,
Adrian CrawfordI just googled that message and got a link to an article by Bob Dorr who works for PSS supporting SQL Server.
In other words - I suspect this is a SQL Server engine problem, not a SSIS one.

-Jamie|||This sounds like you have a database problem. If it is SQL Server then you should probably post this to the relational engine forum. Again if this is SQL Server, you might try running DBCC on the database to see if that shows any problems.

Matt|||Thanks for the responses, I'll see if anyone knows about this in the database engine forum.
Adrian

Attempt to fetch logical page error

Hello,
I have recently moved some dts packages I had been working on from my development(sql2k5) to production environment(sql2k5). Having come across many configuration related errors, I believed my latest one to be of this type at first. However I'm recieving one I've never seen before:

"Attempt to fetch logical page (1:95152) in database 8 failed. It belongs to allocation unit 72057594043301888 not to 72057594045661184.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly"

This package works fine on the development db, however I don't even know where to start tracking this issue down. Any thoughts? I have tried the SSIS forum and they believe it to be a db engine issue.

Thanks,
Adrian CrawfordThere was a low-level problem with one of my tables involved in the dts on production. I found the specific table by running DBCC checkdb. At that point I dropped and recreated the table which has fixed the problem.
Adrian