...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Example:
...
curl
...
--location
...
--request GET 'https://clicktime.symantec.com/3NUzcQdPYLtkF2wuYyG4Jtd7Vc?u=https%3A%2F%2Fyour.api'
...
--header 'ioreadtimeout: 300000'
...
Please use reasonable timeout values when using this override as it does impact performance on the gateway.
...
The API Gateway can handle up to 36000000 (1 hour) as maximum override.
Max Reply Message Size
The API Gateway
...
has a maximum reply message size of 300mb. If the size is exceeded the following error is returned:
ERROR security.service.eagle_api 500 Internal Server Error: 500routing routing to backend failed.
API Gateway – MC2 Entitlements
The effective front end user name should be passed to MC2 with the http header x-eagle-user-id
MC2 ReST processing will include the user's Business Group in the request passed along to the extract,
...
unless the user is a super user. The Business Group will function as an entity filter during the execution
...
of the extract.
...
The one exception is the paceolap feedtype via the eql endpoint, which uses the front end user configured
...
in the EDS UI Vendor Configuration under the pace vendor
...
ID.
A user's BusinessGroup is cached within MC2.
The cache has a time to live of 3 hours (pre February 2021 release) or 1 hour (February 2021 release). If needed, the cache may be refreshed immediately by reinitializing the MC2 rule cache.