CustomSecuritySample: Still Windows authentication after changes about reporting-services HOT 5 CLOSED

Hi Daniel,

Based on your changes, just restarting the service and your browser should be sufficient. You can also try to hit the /reportserver endpoint to check if the issue is specific to the portal or to both endpoints.

This initial login is defined basically by the entry in the web.config, you can check in the server logs for which AuthenticationType is actually being loaded.

Do you have any other SSRS instances installed in this machine?

Thanks
-Boreki

from reporting-services.

@gboreki Thank you for feedback.
I looked at the logs after I entered /ReportServer endpoint and I think I have missed one thing because the logs that was written to was not inside C:\Program Files\Microsoft SQL Server\MSRS13.SQL2016\Reporting Services\LogFiles but instead inside C:\Program Files\Microsoft SQL Server Reporting Services\RSServer\LogFiles

Does this imply that I should add the CustomSecuritySample DLL inside C:\Program Files\Microsoft SQL Server Reporting Services\RSServer\ReportServer rather than C:\Program Files\Microsoft SQL Server\MSRS13.SQL2016\Reporting Services\ReportServer?

I have only one instance installed according to Reporting Services Configuration Manager.
Worth noting is that I'm using the preview build including Power BI.

from reporting-services.

The preview doesn't support multi instance, you will have only the RSServer instance and there is where you need to do the changes.
Also being a preview not all the features supports custom authentication

from reporting-services.

This was the reason. When I changed the Standalone instance and restarted the services the logon page shows up. Case closed.

Thank you very much for your help.

Kind regards
Daniel

from reporting-services.

When i register a user that user is not get admin is a normal user and i need that user as admin.
can someone help me please

from reporting-services.