Hi @fabio78, the architecture remains the same as previous versions. You can implement custom authentication by creating a Security Extension using .NET and registering it in the Report Server configuration. There is no native web form login feature, so you must build it yourself.
Steps to Configure Custom Authentication
Here’s the high-level process:
1. Develop a Custom Security Extension
- Create a .NET class library implementing the following interfaces:
- IAuthenticationExtension
- IAuthorizationExtension
- These handle:
- Authentication: Validate user credentials from your web form.
- Authorization: Define roles and permissions.
2. Deploy the Extension
3. Configure the Login Page
- Create a custom ASP.NET page for login.
- On successful login, issue an authentication cookie or token that your extension validates.
- Redirect users to the Report Server portal.
4. Restart Services
- Restart the Power BI Report Server service after changes.
Important Considerations
- No official support for forms authentication out-of-the-box; everything is custom.
- Ensure HTTPS is enabled for security.
- Test thoroughly because custom extensions bypass standard Windows security.
- Keep in mind that Power BI Report Server does not support Azure AD authentication—only custom or Windows.
References:
Extensions security for Azure Arc-enabled servers - Azure Arc | Microsoft Learn
Security extensions overview - SQL Server Reporting Services (SSRS) | Microsoft Learn
If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.
Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.
If this response was helpful in any way, I’d gladly accept a kudo.
Please mark it as the correct solution. It helps other community members find their way faster.
Connect with me on LinkedIn
