OHDSI Home | Forums | Wiki | Github

Calling all Atlas Security experts!


I am working on a new version of Broadsea (Dockerized Atlas/HADES) that will add easier setup of Atlas/WebAPI with security enabled (among other conveniences) to reduce the burden of sites’ IT/admins on standing up the OHDSI stack.

I have worked with AD and LDAP before, so I have these covered. However, I am looking for experts on the following security providers to assist in establishing settings templates and documentation for this new Broadsea version.

  1. Kerberos
  2. OpenID
  3. CAS
  4. OAuth
  5. IAP

If you have successfully set up Atlas with any of these, please reply here / DM me. All assistance is greatly appreciated!


1 Like

Not an expert, but I summarized my experience with CAS: Tips for configuring CAS 2.0 SSO

1 Like

Thanks @Dillo! I will review.

Do you have CAS at your site and the ability to run docker? If so, would you mind being a tester of this new Broadsea version?

I have a local Fusion VM for testing Ansible scripts for complete deployments of Docker, Miniconda, and the Postgres and last generation consolidated WebAPI/Atlas containers. Time permitting, I’d be willing to look at it.

1 Like

Any other SMEs on Kerberos, OpenID, OAuth, or IAP?

For small Foundations with natural history datasets, that are not fully wired with standard authentication methods, it would be useful to have a Local Auth security enabled by default. I would be more than willing to help test such a setup/scenario.


Thanks! There is a “basic” auth that uses the webapi postgres instance for this purpose. I’ll reach out to you soon on testing this flavor of security.

1 Like