NGINX auth_request directive could handle 200 response from NJS module in the past. (I haven't checked the N+ version.) However, It returns only 401 although NJS returns 200.
To successfully manage OIDC session for the Private/Public/Partner API of NGINX ACM & Developer Portal, this needs to be either fixed or implemented by other ways.
AC:
Investigate the root cause why NGINX auth_request directive return 401 from the 200 response of NJS.
Try session management without using auth_request.
OIDC Ref. Implementation: Either fix N+ auth_request with NJS or enhance new way of session management.
Implement the logic in the ACM & Developer Portal if necessary.
Background:
auth_requestdirective could handle 200 response from NJS module in the past. (I haven't checked the N+ version.) However, It returns only 401 although NJS returns 200.AC:
auth_requestdirective return401from the200response of NJS.auth_request.auth_requestwith NJS or enhance new way of session management.