Hi All,
We have initially set our authentication type to <RSWindowsBasic> to take advantage of the <DefaultDomain> attribute that is exclusively available through this method. We have low low low low level external users/clients who would never be able to understand that they would need to change from the default user and write domain\username.
This was working fine until we recently started to install MS CRM 2011 which required that we insert the <RSWindowsNegotiate> tag in our authentication scheme. I'm new to authentication so I figured I'd give it a shot and I inserted the <RSWindowsNegotiate> tag over the <RSWindowsBasic> tag. This allowed CRM to interface with our Report Server, but left our poor users scratching their heads and tapping at the screen at the prospect of inserting the domain once again. I've since removed the <RSWindowsNegotiate> tag to get the users back on track, but I'm going to need a solution that will keep login simple as well as allow CRM to jive with the report server.
My question is this: What authentication method is best for me?
I've been looking into Custom Authentication/Forms Based Authentication (are they the same thing?) and it looks like a very complicated ordeal. All of my users have windows profiles/passwords established on our domain in our Active Directory, and I'm unsure if Custom authentication allows you to authenticate against Windows credentials (what I've read so far points toward the creation of a credentials database on the SQL server to authenticate against). I'm also unsure if Custom authentication even allows you to specify a default domain or if I'd be able to include whatever CRM "needs" from the <RSWindowsNegotiate> method.
Thank you for reading my long post! I appreciate any input you may have to offer!
- Jim
**EDIT: We're using SQL 2008 R2