For deployments in a cloud environment, user authentication is often upstream of OHDSI tools, including Atlas. By convention an HTTP header can be provided by a reverse proxy, containing the email address of the authenticated user. I suggest that 'X-Remote-User' could be the header name used for this purpose, but I'm not being prescriptive; perhaps it should be a configuration option, that, when left unset doesn't enable this feature.
If this is an easy feature to implement, it is high value, especially for institutions that already have validated security procedures that use reverse proxy authentication.
For deployments in a cloud environment, user authentication is often upstream of OHDSI tools, including Atlas. By convention an HTTP header can be provided by a reverse proxy, containing the email address of the authenticated user. I suggest that 'X-Remote-User' could be the header name used for this purpose, but I'm not being prescriptive; perhaps it should be a configuration option, that, when left unset doesn't enable this feature.
If this is an easy feature to implement, it is high value, especially for institutions that already have validated security procedures that use reverse proxy authentication.