Description
The x509 needs to be ported to the new architecture introduced in #117. The ideal x509 workflow will be revisited in a later release #140 , however for the initial releases, we will stick to the following:
- Browser request made to rucioAuthServer directly ( bypassing gateway). The response from
/auth/x509_web endpoint is handled in the page itself, instead of the presentation layer.
- The page then makes a request tot he NextJS server ( POST /api/auth/x509) with the rucioAuthToken in the body.
- The NextJS server sets the session
Motivation
No response
Change
No response
Additional Information
Description
The x509 needs to be ported to the new architecture introduced in #117. The ideal x509 workflow will be revisited in a later release #140 , however for the initial releases, we will stick to the following:
/auth/x509_webendpoint is handled in the page itself, instead of the presentation layer.Motivation
No response
Change
No response
Additional Information