fc.batch.auth.expiry.code
Setting
Changed on:
24 Oct 2023
| Setting Area | Workflow, Orders, UI component |
|---|---|
| Supported context levels: | ACCOUNT |
Overview
Previously, customers had an impact by an edge case in our authentication token expiry, which would occur when authentication expires while a batch job was in progress. The platform the HTTP response code of 500 instead of 401. This issue has now been fixed, and a 401 response code will return when the authentication token expires while running a batch job.
To ensure backward compatibility, we have implemented a to toggle between the correct (i.e. return 401 HTTP response code) and previous (i.e. return 500 HTTP response code) functionality. The details are mentioned in this document.
Values
| Data Type | Values |
|---|---|
| INTEGER | Possible value:
|
Configuration example
1POST {{fluentApiHost}}/graphql
2
3mutation CreateSetting {
4 createSetting(input: {
5 name: "fc.batch.auth.expiry.code",
6 valueType: "INTEGER",
7 value: 401,
8 context: "ACCOUNT",
9 contextId: 0}) {
10 id
11 name
12 }
13}Update example
1POST {{fluentApiHost}}/graphql
2
3mutation updateSetting {
4 updateSetting(input: {
5 id: 5001464,
6 name: "fc.batch.auth.expiry.code",
7 valueType: "INTEGER",
8 value:500,
9 context: "ACCOUNT",
10 contextId: 0}) {
11 id
12 name
13 }
14}
15