-
Type:
Change Request
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 7.4.8
-
Component/s: Frontend (F), Server (S)
-
None
After fixing ZBXNEXT-8425 a similar issue is comming. More and more applications using Bearer-Token, which are much longer than the current limit.
At the moment we ne use HTTP Agent -> Headers and Add Name: Authorization; Value Bearer <TOKEN> .. it cuts after ~2000 chars, but for example [Veeam Backup and Replication API Login
| https://helpcenter.veeam.com/references/vbr/13/rest/1.3-rev1/tag/Login#operation/CreateToken] using a much longer Bearer token which is more than 4k chars large.. |
curl -s -k -X POST https://veeambackup.internal.domain.de:9419/api/oauth2/token -H 'Content-Type: application/x-www-form-urlencoded' -H 'x-api-version: 1.3-rev1' -d grant_type=Password -d username=A_USERNAME -d 'password=SECRETSHIT' -d refresh_token=string -d code=string -d use_short_term_refresh=true -d vbr_token=string |jq '.access_token' |wc -c 4366
Would be great if you can increase the value fields..