TUI access ends with Authorization error - HTTP 403 Forbidden

[x-heii]

We have installed Janssen v1.2.0 in the AWS EKS environment.
Installations looks ok. Database is in MySQL AWS database cluster.

After device authentication, the TUI client does not display anything from the db and prints the following error to the Jans config API debug log:

OpenIdAuthorizationService.java:81- Verify if JWT jans-config-api - 14-01 12:39:20.858 ERROR jans.configapi.util.JwtUtil JwtUtil.java:53- Not jwt token fb07eb40-9b36-4e61-a28d-f9ae6ff772af jans-config-api - 14-01 12:39:20.858 INFO configapi.security.service.OpenIdAuthorizationService OpenIdAuthorizationService.java:100- Token is NOT JWT hence introspecting it as Reference token jans-config-api - 14-01 12:39:20.860 INFO configapi.security.service.OpenIdService OpenIdService.java:57- oAuth Final introspectionUrl:https://auth.test.com/jans-auth/restv1/introspection jans-config-api - 14-01 12:39:20.877 ERROR jans.configapi.filters.AuthorizationFilter AuthorizationFilter.java:94- ======AUTHORIZATION FAILED =========================================== org.jboss.resteasy.client.exception.ResteasyForbiddenException: HTTP 403 Forbidden at org.jboss.resteasy.client.exception.WebApplicationExceptionWrapper.wrap(WebApplicationExceptionWrapper.java:77) ~[resteasy-client-api-6.0.3.Final.jar:6.0.3.Final] at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.handleErrorStatus(ClientInvocation.java:268) ~[resteasy-client-6.0.3.Final.jar:6.0.3.Final]
Same error happens when using the Jans Config API with curl commands.

What could be causing this or is it a bug that is not found yet?

[mzico]

I am going to test it locally...

[ossdhaval]

@x-heii Thank you for sharing this.

This is an observation on an old release. Should be reconfirmed on the latest release 2.2.0.

For now, I am closing this as outdated. Please create a new discussion if this is still an issue.