github-actions[bot]
commented
2 months ago There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
Is your feature request related to a problem? I need to be able to have the username come from an HTTP header via HTTP proxy. Tracing through the code, this functionality got removed between 13 and 14 (or perhaps not "removed" - it might just have never been migrated).
Describe the solution you'd like I want to provide a remote user name via HTTP header, preferably that I've specified. It will be in the form of an e-mail address. I then want ODOO to match the given ODOO user, and not let them in if there is no match. Then, normal user configuration will set the role and permissions.
Describe alternatives you've considered I thought about trying to use SAML2 directly but there's a proxy so it's easiest if I can just let the proxy (which is apache2 in this case) handle the SSO and just pass the resulting username on to ODOO.
Additional context In my particular case, the backing is shibboleth, but for a number of reasons it's best to leave the SAML2 at the proxy.