Anubis still on the API path?

This is post #1271 (closed)

I've just had a user reporting an error with their datawarehouse upload, which happened post https://gitlab.cee.redhat.com/kernel-qe/sustaining-engineering/seqe/-/merge_requests/170 which logs the headers

seqe.beaker dw-upload 12337994
ERROR:seqe.dw:CSRF Token not found
ERROR:seqe.dw:Response: 200
ERROR:seqe.dw:Headers: {'cache-control': 'no-store', 'content-encoding': 'gzip', 'content-type': 'text/html; charset=utf-8', 'set-cookie': 'techaro.lol-anubis-auth=; Path=/; Domain=datawarehouse.cki-project.org; Expires=Tue, 24 Feb 2026 08:32:39 GMT; Max-Age=0; Secure; SameSite=None, techaro.lol-anubis-cookie-verification=019c8ec8-53bc-7ee8-96c4-e0e9d3faf2ad; Path=/; Domain=datawarehouse.cki-project.org; Expires=Tue, 24 Feb 2026 09:03:39 GMT; Secure; SameSite=None', 'date': 'Tue, 24 Feb 2026 08:33:39 GMT', 'transfer-encoding': 'chunked'}

So it appears we are getting an anubis response to our call to .../oidc/authenticate/

Is it possible this has regressed for some reason? Is it possible to check logs to see why this response may have come back?

Jira: CKI-7278