Hello laeira,
Thanks for the detailed information.
The fact that Keycloak successfully returns an access token is important.
This means that the initial login and redirect to Keycloak are working.
The error occurs afterwards, when ReportServer tries to validate the token.
There is a relevant change in newer Keycloak versions which could explain this behavior.
The ReportServer installation guide currently uses Keycloak 26.5.1. Starting with Keycloak 26.6.2, token validation became stricter: the ReportServer backend client (rs) must be included in the access token’s aud (audience) claim.
Since your setup stopped working after upgrading Keycloak to 26.7.3, this is the first thing we would check.
Could you please decode the access token locally and tell us the values of:
aud
azp
iss
Please do not post the complete token or any client secrets.
In particular, please check whether rs is listed in the aud claim.
As a diagnostic test, you can also temporarily enable “Allow token introspection without audience check” for the rs client in Keycloak.
If ReportServer login works again after enabling this option, this would strongly indicate that the changed audience validation in Keycloak is the cause.
This option should only be used for testing. If this proves to be the issue, the proper solution is to configure the Keycloak token so that the rs client is included in its audience.
At this point, we would therefore not classify this as a ReportServer bug yet. First, let’s verify whether the Keycloak upgrade changed the token validation behavior in this setup.
Thank you very much for your patience and cooperation.
Kind regards,
Jasmin