Requesting an access token or configuration fails when using things on ForgeOps.
Any request made to the `/things` endpoint fails with an "invalid request" error when SSL is terminated at the load balancer/ingress.
The issue can be seen when Things are enabled for the Identity Platform with ForgeOps.
No workaround is available.
This is due to the JWT Proof of Possession audience validation that occurs in AM when a PoP restricted SSO token is used for a request.