Details
-
Task
-
Status: In progress (View Workflow)
-
TBD
-
Resolution: Unresolved
-
None
-
None
-
None
-
-
stripes-force 172, stripes-force 173, stripes-force 174, stripes-force 175
-
Stripes Force
-
Poppy (R2 2023)
-
TBD
Description
Summary: leverage cookie-based authentication in all API requests, removing the request header x-okapi-token and adding the request option credentials: "include" in all FOLIO API requests.
./stripes-core/src/discoverServices.js: 'X-Okapi-Token': token, ./stripes-core/src/withOkapiKy.js: request.headers.set('X-Okapi-Token', token); ./stripes-core/src/createApolloClient.js: 'X-Okapi-Token': token, ./stripes-core/src/loginServices.js: 'X-Okapi-Token': token, ./stripes-core/src/loginServices.js: const token = resp.headers.get('X-Okapi-Token') || ssoToken; ./stripes-core/src/useOkapiKy.js: request.headers.set('X-Okapi-Token', token); ./stripes-core/src/components/CreateResetPassword/components/PasswordValidationField/PasswordValidationField.js: ? { headers: { 'x-okapi-token': token } } ./stripes-core/src/components/CreateResetPassword/CreateResetPasswordControl.js: 'x-okapi-token': token,
TestRail: Results
Attachments
Issue Links
- relates to
-
STCOR-484
implement client-side handling of refresh tokens
-
- In progress
-