Greetings, OHDSI Community,
We are pleased to announce that Atlas 3.0 and WebAPI 3.0 have entered the release-candidate phase as we approach the final 3.0 release.
This is a major update to the Atlas and WebAPI platform. WebAPI 3.0 modernizes the underlying application framework and introduces a new authentication and authorization architecture. Highlights include:
- Migration from Shiro to Spring Security, with authorization enforced across protected API endpoints
- Fine-grained, entity-level access control for Atlas resources
- Updated authentication options, including OAuth/OIDC support, role mapping at login, API keys, and administrative RunAs capability
- Reintroduction of Pathway Characterization, Cohort Characterization, Feature Analysis, and Incidence Rate Analysis functionality
- Modernized platform dependencies, including Spring Boot, Spring Batch, Flyway, Tomcat/Jakarta compatibility, and updated database migrations
- Removal of internationalization responsibilities from WebAPI; localization is now handled by the Atlas user interface
Important upgrade notice: WebAPI 3.0 includes substantial database, security, permissions, and migration changes. Organizations upgrading an existing Atlas/WebAPI 2.x environment should make complete, tested backups of all relevant databases before beginning an upgrade. This includes the WebAPI configuration database and any related security or authentication data. Please treat an upgrade to 3.0 as a planned migration and validate it in a non-production environment before deploying to production.
To evaluate the release candidates from source, use the develop branch of Atlas3 together with the webapi-3.0 branch of WebAPI. Broadsea will also available for users who prefer a Docker-based WebAPI 3.0 environment (coming soon).
Installation and configuration instructions are available in the WebAPI Installation Guide. Please refer to that guide rather than relying on this announcement for deployment details.
The complete technical change summary and primary release notes are maintained in WebAPI pull request #2536.
We welcome community testing and feedback during the release-candidate period.