For anyone facing this same issue, I found the solution here: Invalid access token payload, jwt encrypted with A256GCM
It was indeed due to the audience not properly configured.
For anyone facing this same issue, I found the solution here: Invalid access token payload, jwt encrypted with A256GCM
It was indeed due to the audience not properly configured.