Skip to content

v2.18.0

Compare
Choose a tag to compare
@stevenolen stevenolen released this 31 Mar 19:56
· 11 commits to master since this release

The 2.18.0 release contains a number of new features and bugfixes:

  • Access Request APIs: A new set of APIs to handle users requesting particular permissions in ohmage. Please see the docs for details.
  • Support for keycloak authentication: By way of the keycloak identity manager, ohmage now supports SSO via oauth2, SAML 2.0, ldap and others. This is a major new feature which requires additional processes to use. Please see the wiki page for a FAQ/explanation if you're interested in implementing!
  • With external authentication now available, local authentication can be completely disabled.
  • survey responses are now editable (if enabled at the campaign level) by using the update=true parameter when performing a survey upload. Please see the documentation for implementation changes.
  • survey responses can now have their privacy state set on initial upload. Please see the documentation for implementation changes.
  • campaign/read (with output_format=long parameter) now provides a count of shared/private responses available to the user making the request.
  • Integrated docker builds are now available to more easily get started as a power user/developer. These will eventually replace existing builds found on the docker hub and offer the best supported ohmage environment.
  • the app_name parameter is now read from the preferences table in the database if available (instead of having to be compiled into the war file)
  • dependencies on deploying with tomcat7 have been removed.
  • [BUGFIX] Users who self-register and are added to the public class are now also added as "analysts" (which allows public users to see other public user data). Previously users were only able to see their own data, leading to an awkward use in servers with "public"-like data collection.
  • [BUGFIX] Annotation APIs now function as intended.
  • [EXPERIMENTAL!] undocumented user/setup_external api is now available for managing external users prior to their first log in. Only available to users with the user_setup parameter while keycloak authentication is enabled.

Some final notes:

  • As of the 2.17 release, the manual sql upgrade process was deprecated, meaning that the database schema changes in 2.18 must be done via the flyway migration method. Please see the db/ directory for more details: https://github.com/ohmage/server/tree/master/db
  • The 2.18 release also marks the beginning of a new github flow, where the master branch will now contain the latest, reasonably stable code, and not actual releases. Please see the releases area for pre-compiled releases and specific release tags.