MGW is publishing events to the Analytics server with a '0' value as the request timestamp. Because of this, the Analytics server will not be able to complete the aggregation accurately.
This can be reproduced when an opaque token is used to invoke an API in MGW while keeping the JWT token configurations. In the MGW logs the following error can be seen.
ERROR [ballerina/oauth2] - Failed to call the introspection endpoint. : error {ballerina/http}GenericClientError message=Something wrong with the connection cause=error {ballerina/io}GenericError message=Connection refused: localhost/127.0.0.1:9443
It seems with this error the MGW is publishing a malformed event which is not designed to be published.
Steps to Reproduce
This can be reproduced when an opaque token is used to invoke an API in MGW while keeping the JWT token configurations. In the MGW logs the following error can be seen.
Description
MGW is publishing events to the Analytics server with a '0' value as the request timestamp. Because of this, the Analytics server will not be able to complete the aggregation accurately.
This can be reproduced when an opaque token is used to invoke an API in MGW while keeping the JWT token configurations. In the MGW logs the following error can be seen.
ERROR [ballerina/oauth2] - Failed to call the introspection endpoint. : error {ballerina/http}GenericClientError message=Something wrong with the connection cause=error {ballerina/io}GenericError message=Connection refused: localhost/127.0.0.1:9443
It seems with this error the MGW is publishing a malformed event which is not designed to be published.
Steps to Reproduce
This can be reproduced when an opaque token is used to invoke an API in MGW while keeping the JWT token configurations. In the MGW logs the following error can be seen.
Version
3.2.7
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response