Release Notes: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
* Native authentication now disables users after 4 invalid login attempts, either password or MFA code if applicable. Invalid attempts threshold is configurable. | * Native authentication now disables users after 4 invalid login attempts, either password or MFA code if applicable. Invalid attempts threshold is configurable. | ||
* Stronger licensing controls. Site and hardware licenses as of this version must be regenerated by Carfey Software and every 2 years. Contact us at licensing | * Stronger licensing controls. Site and hardware licenses as of this version must be regenerated by Carfey Software and every 2 years. Contact us at licensing [[Image:atSymbol.png]] obsidianscheduler.com. | ||
=== Bug Fixes === | === Bug Fixes === | ||
Revision as of 01:17, 7 March 2025
Please review our Upgrade Instructions.
Read about our Planned Releases.
Looking for old release notes? See Release Notes - Older Releases.
Obsidian 6.1.0
Released March 2025
Features / Enhancements
- Native authentication now disables users after 4 invalid login attempts, either password or MFA code if applicable. Invalid attempts threshold is configurable.
- Stronger licensing controls. Site and hardware licenses as of this version must be regenerated by Carfey Software and every 2 years. Contact us at licensing
obsidianscheduler.com.
Bug Fixes
- Native authentication password complexity pattern properly created and no longer overwritten on restart.
Obsidian 6.0.1
Released February 2025
Features / Enhancements
- File Archive Job and File Scanner Job both now support min/max file sizes and minimum age.
Bug Fixes
- Native authentication user updates now support long passwords.
Obsidian 6.0.0
Released December 27, 2024
Features / Enhancements
- Jakarta Servlet 5.0
- Servlet container for Web Admin must support Jakarta Servlet 5.0 (e.g. Tomcat 10, Jetty 11)
- Micronaut integration support
- Groovy 4 support
- Yaml configuration support[1]
- Native authentication supports customizable password complexity requirements
- XML support deprecated across the product including XML UI downloads, XML runner configurations and XML license leases.
- Starting January 1st 2027, XML license lease requests will stop being processed. All Obsidian instances running using internet-verified licenses (including licence key proxies) will be required to use release 6.0.0 or later as of January 1st 2027.
- Above noted XML support will be removed in the first Obsidian version released in 2027.
- License leases use JSON payloads.
Obsidian 5.5.1
Released December 16, 2024
Bug Fixes
- Admin only (no scheduler) UI no longer generates event hook errors while running nor during shutdown
- Quick start installer file no longer generates errors during installation
- A few small web UI enhancements
Obsidian 5.5.0
Released October 2024
Features / Enhancements
- Event Hooks management available in UI, Embedded API and REST API.
- Installer supports custom add on configurations Potential breaking change to automated installer files. [2]
Bug Fixes
- Certain Cron expressions that fail to generate text descriptions no longer impact scheduling.
- Text database columns were previously restricted to maximum length of MySQL implementation. Corrected to validate length via DB implementation.
Obsidian 5.4.0
Released June 2024
Features / Enhancements
- Event Hooks available in Embedded API and REST API.
- GSON library upgrade to support Java 21
Bug Fixes
- Oracle identifier no longer too long when using prefixes.
Obsidian 5.3.0
Released March 2024
Features / Enhancements
- New Event Hooks Status available in the UI.
Bug Fixes
- Some improvements throughout the Admin Web Application for autofocus of fields.
- Additional classes and interfaces added to javadoc.
- Some cleanup in javadoc documenation.
Obsidian 5.2.1
Released January 2024
Features / Enhancements
- Maintenance Jobs are now scheduled by default in new installations. Can be disabled via Configuration property.
- New Standard Output/Error Streams Event Hook.
Bug Fixes
- Schedule descriptions are now updated after edits are applied in all UI screens and APIs.
Obsidian 5.2.0
Released December 2023
Features / Enhancements
- Cron & Recur patterns along with any use of Schedule Aliases now support plain language description of the patterns throughout the UI, visible while hovering patterns, and in REST and Embedded API responses.
- All screens supporting UI exports now support JSON (Job Activity, Jobs, Runtime Previews, Job Chains, Logs, Sent Notifications, Users, Calendars)
- All screens supporting UI exports and search criteria and/or inline filters now include any specified search criteria and filter text in Excel, XML and JSON downloads (Job Activity, Jobs, Runtime Previews, Job Chains, Logs, Sent Notifications, Users)
- Support for Jakarta EE mail Potential breaking change to automated installer files. [3]
- New REST Endpoint Event Hook
- Key Server proxy artifact obtained via web download during installation
Bug Fixes
- Time picker buttons (hour, minute, AM/PM) in Job Activity filtering no longer change other elements of the selected time.
- Cron pattern with LW and any other non-L value in day position no longer also incorrectly evaluates to last day.
Obsidian 5.1.1
Released June 2023
Bug Fixes
- Native authentication no longer fails when user deletes are attempted from the UI.
- Built in maintenance job Job History Cleanup no longer leaves deletion candidate CHAIN SKIPPED records in the JOB_HISTORY table in rare circumstances.
Obsidian 5.1.0
Released April 2023
Features / Enhancements
- Schedule Aliases now support fragments for configuration-time substitutions.
- New convenience job Database File Export Job for generating basic file extracts from database queries.
- New convenience job REST Invocation Job for making simple REST calls and storing results.
- Performance improvements in job failure handling.
Obsidian 5.0.4
Released February 2022
Features / Enhancements
- Log4j2 2.17.1 as fix for RCE vulnerability where attackers can modify log4j configuration.
- Restore missing default log4j2 configuration in installation artifacts.
Obsidian 5.0.3
Released December 2021
Features / Enhancements
- Log4j2 2.17.0 as fix for DOS vulnerability
- Fix native login issue showing as inactive on some databases.
Obsidian 5.0.2
Released December 2021
Features / Enhancements
- Log4j2 2.16.0 as permanent fix for RCE vulnerability
Obsidian 5.0.1
Released December 2021
Features / Enhancements
- Log4j2 2.15.0 as fix for RCE vulnerability
Bug Fixes
- Fix sporadic native login issue on some databases.
- Formatting fix in quick installer file
Obsidian 5.0.0
Released August 2021.
Features / Enhancements
- Java 11 (minimum Java version)
- Schedule Aliases including support in REST API and Embedded API
- MFA Support for UI logins
- New Author and Operator roles
- Convention-based role permissions by root job folder for Write, Author and Operator.[4]
- Bundled Jetty 10.0.2
- Legacy Embedded API (from Obsidian 1.5) dropped
- Signal handler disabled by default. Enabled only via configuration.
- Many library upgrades.
- UI javascript library updates.
Footnotes
- ↑
If you are using automated installer files from previous releases, you will need to add an additional configuration item to choose between yaml and properties formats in UserInputPanel.0.
<com.izforge.izpack.panels.UserInputPanel id="UserInputPanel.0"> <userInput> ......snip...... <entry key="config.format" value="yaml" /> OR <entry key="config.format" value="properties" /> ......snip...... </userInput> </com.izforge.izpack.panels.UserInputPanel> - ↑
If you are using automated installer files from previous releases, you will need to add a new section of xml as of Obsidian 5.5.0 to handle a new UserInputPanel. Immediately after the UserInputPanel.17 closing brace, add the following:
<com.izforge.izpack.panels.UserInputPanel id="UserInputPanel.18"> <userInput> <entry key="extra.log4j2.properties.1" value=""/> <entry key="extra.log4j2.properties.2" value=""/> <entry key="extra.log4j2.properties.3" value=""/> <entry key="extra.log4j2.properties.4" value=""/> <entry key="extra.log4j2.properties.5" value=""/> <entry key="extra.log4j2.properties.6" value=""/> <entry key="extra.log4j2.properties.7" value=""/> <entry key="extra.log4j2.properties.8" value=""/> <entry key="extra.log4j2.properties.9" value=""/> <entry key="extra.log4j2.properties.10" value=""/> <entry key="extra.log4j2.properties.11" value=""/> <entry key="extra.log4j2.properties.12" value=""/> <entry key="extra.log4j2.properties.13" value=""/> <entry key="extra.log4j2.properties.14" value=""/> <entry key="extra.log4j2.properties.15" value=""/> <entry key="extra.log4j2.properties.16" value=""/> <entry key="extra.log4j2.properties.17" value=""/> <entry key="extra.log4j2.properties.18" value=""/> <entry key="extra.log4j2.properties.19" value=""/> <entry key="extra.log4j2.properties.20" value=""/> <entry key="extra.carfey.properties.1" value=""/> <entry key="extra.carfey.properties.2" value=""/> <entry key="extra.carfey.properties.3" value=""/> <entry key="extra.carfey.properties.4" value=""/> <entry key="extra.carfey.properties.5" value=""/> <entry key="extra.carfey.properties.6" value=""/> <entry key="extra.carfey.properties.7" value=""/> <entry key="extra.carfey.properties.8" value=""/> <entry key="extra.carfey.properties.9" value=""/> <entry key="extra.carfey.properties.11" value=""/> <entry key="extra.carfey.properties.10" value=""/> <entry key="extra.carfey.properties.12" value=""/> <entry key="extra.carfey.properties.13" value=""/> <entry key="extra.carfey.properties.14" value=""/> <entry key="extra.carfey.properties.15" value=""/> <entry key="extra.carfey.properties.16" value=""/> <entry key="extra.carfey.properties.17" value=""/> <entry key="extra.carfey.properties.18" value=""/> <entry key="extra.carfey.properties.19" value=""/> <entry key="extra.carfey.properties.20" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel>
- ↑
If you are using automated installer files from previous releases and had email configured, you will need to add a new section of xml as of Obsidian 5.2.0 to handle a new UserInputPanel. Immediately after the UserInputPanel.16 closing brace, add the following:
<com.izforge.izpack.panels.UserInputPanel id="UserInputPanel.17"> <userInput> <entry key="mail.type.selection" value="javax"/> </userInput> </com.izforge.izpack.panels.UserInputPanel> - ↑ There is a possibility of a breaking change to Embedded or REST API use due to the need to change the User Role enumeration from a Java enum to an enum-style class to support this feature. Bringing in the upgraded Obsidian library and compiling should reveal any such broken use of these enumerations. Needed changes should be minor and self-explanatory.
