AI GW: add integration test for the entire flow: issuing a user token + accepting it for CS
Problem to solve
We currently don't have an integration test that checks the combination of issuing a user token and the ability to accept that token for the CS endpoint.
It would be beneficial to have this test as it will reflect the lifecycle of the user token.
This test may prevent issues with the signing keys similar to Slack, internal when there was inconsistency between encoding and decoding keys.
Proposal
We need to add another test.
Let's make sure it fails if, for example, AIGW_SELF_SIGNED_JWT__SIGNING_KEY
is used for encoding the user token and some other key (fake one) is used for decoding the token.
Further details
TBD
Links / references
Edited by Aleksei Lipniagov