January 24, 2014 at 6:36 am
Hi folks,
We have in-house a BI Server with SSRS instances installed and each SSRS instance connects to a clustered database server where its own database is hosted. Although I can make successful connections directly from the Reporting Services Server to the database (and thus work normally) clients cannot connect from their workstations to the reporting server.
I have decided to use a domain-based account for the service account rather than the networkservice account because it falls in line with our security concept. The problem with this approach seems to be in the handling of the Kerberos token for the authentication method.
After some research I found that a .xml file called rsreportserver.config needed to be altered because I am using a domain-based account instead of a localnetwork account. The change that needed to be made in order to make this reporting server compatible with our requirements was the following:
<AuthenticationTypes>
<RSWindowsKerberos/>
<RSWindowsBasic/>
<RSWindowsNTLM/>
<RSWindowsNegotiate/>
</AuthenticationTypes>
In addition to altering this code our network admins had to register the SPN for the user that will authenticate. I am not sure if the admins have done this correctly but the concrete fact is that it still doesn't work.
Can anyone help with this problem or maybe even give me a hint on how the SPN shuld be entered in order for it to work?
Many thanks in advance,
Kev
February 27, 2014 at 6:54 am
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply