[NXP-32514] use Keycloak auth after Automation basic auth in specific auth chains - Nuxeo Issue Tracker

XML

Word

Printable

Release Notes Summary:
Automation basic auth now precedes Keycloak auth in specific auth chains
Tags:
- nxplatform
- security
Upgrade notes:

Hide

Now when doing automation or rest calls, Automation basic auth precedes Keycloak auth. This brings change to the response status codes to expect.

These have been documented in the Nuxeo Keycloak documentation alongside with a sample xml contrib to reverse back the auth plugins order to the older state.

Show
Now when doing automation or rest calls, Automation basic auth precedes Keycloak auth. This brings change to the response status codes to expect. These have been documented in the Nuxeo Keycloak documentation alongside with a sample xml contrib to reverse back the auth plugins order to the older state .
Team:
PLATFORM
Sprint:
nxplatform #112
Story Points:
1

We want to privilege Automation basic auth plugin's responses' status codes in specific auth chains (RestAPI, Automation)

Some documentation about status codes has been written in ~~NXDOC-2663~~
with a sample contribution allowing to put keycloak back up.

is required by

NXP-32389 Fix HTTP 500 when running an unauthenticated request against REST API with Keycloak auth