Skip to main content

2023-q3

QA-Board servers can now authenticate users with single sign-on (SAML) and require a login to see projects. Interrupted runs show as failed, and comparisons prefer reference runs on the same input.

Admins

Single sign-on with SAML

Besides local accounts and LDAP, users can now sign in through a SAML identity provider. Choose the method with QABOARD_LOGIN_TYPE (LOCAL, LDAP or SAML) and configure SAML with the QABOARD_SAML_* variables.

Learn more →
Admins

Require a login

Set QABOARD_LOGIN_REQUIRED=true to block anonymous users: they must sign in before opening a project.

Learn more →

Web app​

  • When matching runs with the reference, the web app and exports now prefer reference runs with the same input path.
  • Stopped batches now mark their interrupted runs as failed, with finer-grained statuses.

CLI and project setup​

  • qa batch --action-on-existing skip no longer skips runs that are still pending: it waits for them instead.
  • The LSF runner no longer uses fast_queue: jobs always go to the configured queue.
  • Absolute input paths are resolved through symlinks.
  • The package now depends on scikit-learn instead of the deprecated sklearn name.

Server and administration​

  • The public sign-up API endpoint is disabled, to prevent unauthorized users from creating accounts.
  • The login settings are baked into the web app image when it is built.
  • nginx forwards the X-Forwarded-* headers that SAML needs, and the development setup can run over HTTPS.
  • The cleanup job falls back to deleting the whole output directory when a run has no file manifest.

Documentation​

  • The server setup page documents user management, sign-in methods and the new login variables.

Fixes​

  • Fixed a directory traversal vulnerability in the nginx configuration for the docs.
  • Fixed regions of interest when the image is zoomed, and the text copied from the ROI viewer.