NOTE: Trivore ID Documentation has moved to https://trivoreid.com

The content on this site IS OUT OF DATE!

This space has been archived!

Please go ahead to the new site!

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Still on track with both adding new features, improving current ones, and fixing any bugs found. The relevant changes are listed below.

This list below is for the next, still unreleased release.

New Features

  1. Added auto-generated authorisation types for suomi.fi-valtuudet YPA in use in Finland.

Improvements

  1. Log new user account creation time initial data for easier troubleshooting. We got bit by this in one site. With this improvement, we have this seldom needed, but necessary data point. Sensitive data is not saved, of course.

  2. Datastorage to and UI in Management UI to review existing datastorages. This is an important toold for troubleshooting, and auditing purposes.

  3. Added more Lock settings boxes to protect from human errors.

  4. Internal code refactoring to gain more speed.

  5. Center all views under OpenID authorisation endpoint (incl. user creation, password forgotten view, error views etc.).

  6. Add support for forced authentication for SAML user directories. This ensures that autentication is performed every time user uses SAML user directory authentication and no previous session information is used. Previous behaviour was to cache authentications for a while (time is dependent on external user directory).

Bug fixes

  1. Related to JWKS servlet, some duplicate and unnecessary dependencies (code regression) were removed. This bug never reached production, as it was catched in-flight during development cycle.

Integrated feature: Product management

  1. Refactoring end-points before feature launch. This was the last time we could do it. Practically /sales was just changed to more descriptive /products. Note, /products is primarily for those who want to define their own WebUI to the product management engine we provide.

  2. Added filtering and data searchabilty.

  3. Added /sales end-point to better support web-shops to quickly retrieve all permitted products and prices.

  • No labels