Release 6.0.1

This release contains but one bug fix, see #250. It is needed to be able to add new tags.

Release 6.0.0

• This release requires Java 25 or later.
• Based on Spring Boot 3.5.7.
• Multiple authentication providers supported, see #247.
• If embedded LDAP is used for authentication, passwords must be bcrypt encrypted in the ldif file.
• Check of HEIC file attachments improved: rather than relying on file name extensions, actual content is inspected for HEIC format.

Release 5.1.2

Fixes a few bugs and adds some new features:

• The service will reject submission of log entries containing HEIC files attachments. HEIC may be the default image format on iPhone, but this format is not supported in Java and most browsers.
• The service supports a web socket endpoint clients may connect to in order to receive messages when new log entries are created. This eliminates the need to poll periodically from the client. Supported clients (Phoebus and browser) have been updated accordingly.
• A RSS feed endpoint has been added: http(s)://<host>:<port>/Olog/logs/rss.
• To handle time zone issues (server and client operating different time zones), the service will consider client supplied tz request parameter in search requests. This parameter should indicate the client's time zone, e.g. tz=GMT-5 or tz=Europe/Paris. Supported clients (Phoebus and browser) have been updated accordingly.
• Documentation for the log entry template feature has been added.

NOTE: This is the last release targeting Java 17. Subsequent releases will require Java 25 to build and run the service.

Release 5.0.4

New features:

Templates
A template shares the structure of a log entry, except for attachments. Templates are persisted in a separate index. Clients may query the service for a list of existing templates. The CS Studio (Phoebus) client has been updated to take advantage of templates. Administrators will need to use other tools (e.g. curl) to manage template data. The service documentation has been updated accordingly.

Levels
Similar to logbooks and tags, the service now also supports management of "levels". This replaces the client side configuration of level values. Administrators will need to use curl or similar to manage level data. Client side should query the service for levels, where each level object also indicates if it is the default level. Only one level object may be inserted as the default level. The service documentation has been updated accordingly.

Release 4.7.6

Major change: support for editing log entries. However, edits are non-destructive as the current state of the entry is archived in separate Elasticsearch index before the update version is persisted.

service-olog-2.0.4

Olog 2.0.4 release