1

I have a pretty complicated situation at hand, let me try to explain.

I have a SQL Server and a Web Server in a separate domain (lets call it domain A).

SQL Server has the databases for Reporting services, The web server has reporting services installed.

The SSRS also have SSL certificates installed and we are using https protocol to connect to the reports manager.

Now I need to give access to users from domain B to connect to the Reports Manager (report server on Domain A).

The users from Domain B cannot have any logins in the Domain A where the reporting services are installed, I know to access the reports manager I need to add domain logins/groups to the reports manager and assign them appropriate roles to access the reports.

What options do I have (if any) to give access to users from Domain B to connect to a Reports Manager on Domain A?

Important Note:

The access to reports server is via NLB with external facing IP, the reports server (web server) or the SQL server does not have any external facing IP

  • Can you setup local (non-domain) users on the Reporting Server? – Max Vernon Oct 13 '15 at 23:54
  • Yes I have already done that, but the problem is when a user from other domain tries to access the reports manager, how that user will be authenticated? The users access the reports manager by just typing in the url , now even if they do put in the local user details they still keep getting prompts for username and password – M.Ali Oct 13 '15 at 23:57
  • @MaxVernon When I try to login to reports manager using local user credentials from the reports server itself it worked for me , but from the cross domain it doesnt work :( very strange. and I am sorry I have forgot to mention a very important point, The access to reports server is via NLB with external facing IP, the reports server (web server) or the SQL server does not have any external facing IP. – M.Ali Oct 14 '15 at 0:05
  • @MaxVernon I have also tried to connect to Reports Manager from the reports server itself using the NLB url i.e https://NLB.name.com/Reports and it prompts me for the username and password, if I used the local username and password it did not work. But if tried to connect to Reports Manager using the local server name it works i.e https://ServerName/Reports it is only from the reports server itself. – M.Ali Oct 14 '15 at 0:12
  • I am speculating, what you are telling wont work - you need to have trust between the domains. Can you create sql server users with same sids for allowing report execution ? – Kin Shah Oct 14 '15 at 0:43
2

I don't recommend it but

You have two options:

  1. Connect using a domain username & password from network A (everyone in network B connecting as DOMAINA/userx)
  2. Allowing anonymous access. (this is inherently dangerous and you would want at a bare minimum to pass something to all of your reports as part of your process for security authentication and probably change the default structure for uploading http://local/reportserver might become http://local/rs)
  • But he did state specifically that "The users from Domain B cannot have any logins in the Domain A where the reporting services are installed" so this would leave an anonymous access situation or else setup a domain trust. – Pimp Juice IT Oct 14 '15 at 2:17
  • He did. However you will need some form of Alias connection to make between the two domains or you have to allow anonymous. – Brodie Brickey Oct 14 '15 at 16:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.