Release Notes: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
Tag: Reverted |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
=== Features / Enhancements === | === Features / Enhancements === | ||
* ''' | * '''Updated third-party libraries''' — Bundled third-party libraries were updated to current releases. See [[Advanced_Configuration#Dependent_Libraries|Dependent Libraries]] for the current list. | ||
* '''JavaScript scripting engine''' — See [[Scripting_Jobs|Scripting Jobs]]. | * '''REST API Postman collection''' — A Postman collection and sample environment for the REST API are included in the release zip and the Documentation pack. See [[REST_API#Postman_collection|REST API]]. | ||
* '''Additional Maven dependencies at install''' — See [[Installation_Guide#Additional_Maven_dependencies|Additional Maven dependencies]]. | * '''JavaScript scripting engine''' — Scripting Jobs bundle OpenJDK Nashorn so JavaScript jobs run on JDK 15 and later. The installer's Script Libraries step has a JavaScript option, cleared by default. See [[Scripting_Jobs|Scripting Jobs]]. | ||
* ''' | * '''Additional Maven dependencies at install''' — An optional installer step adds extra Maven libraries, with their transitive dependencies, to the scheduler WAR and Standalone Runtime from a file or pasted list. See [[Installation_Guide#Additional_Maven_dependencies|Additional Maven dependencies]]. | ||
* ''' | * '''Host Status version''' — Host Status shows each host's Obsidian version and displays a banner when host versions differ from the web UI or from each other. See [[Admin_Host_Status|Admin Host Status]]. | ||
* ''' | * '''Single mail implementation jar''' — Both JavaMail implementations ship in one <code>jdk.jar</code> and <code>obsidian.jar</code>, and the installer's Email Implementation step selects which one is used. See [[Advanced_Configuration|Advanced Configuration]]. | ||
* '''Linux systemd services''' — On Linux, the installer can offer systemd service files for Embedded Tomcat and the Standalone Runtime. The services are not enabled or started automatically. See [[Linux_Service|Linux Service]]. | |||
* '''Log path per installer artifact''' — See [[Installation_Guide#Log_path|Log path]]. | * '''Log path per installer artifact''' — When more than one of the WAR, Admin WAR, and Standalone Runtime is selected, each can have its own optional log path. See [[Installation_Guide#Log_path|Log path]]. | ||
* '''Log4j2 configuration is XML''' — See [[Installation_Guide#Log_path|Log path]]. | * '''Log4j2 configuration is XML''' — The installer generates log4j2 as XML, which you can edit on the Log4j2 XML screen or supply as a sidecar file. See [[Installation_Guide#Log_path|Log path]]. | ||
=== Security Enhancements === | === Security Enhancements === | ||
* '''Updated UI JavaScript packages''' — Many UI npm packages were updated for known security vulnerabilities. | * '''Updated UI JavaScript packages''' — Many UI npm packages were updated for known security vulnerabilities. | ||
* '''Standalone scheduler shutdown hardening''' — See [[Advanced_Configuration|Advanced Configuration]] (standalone stop listener). | * '''Standalone scheduler shutdown hardening''' — The Standalone Runtime stop listener now requires a shared secret and binds to loopback by default. See [[Advanced_Configuration|Advanced Configuration]] (standalone stop listener). | ||
* ''' | * '''OAuth/SAML response hardening''' — OAuth and SAML endpoints set explicit content types, and post-login return URLs are restricted to relative or same-host targets. See [[Authenticator#OAuthAuthenticator_(OIDC_SSO)|OAuthAuthenticator]] and [[Authenticator#SAMLAuthenticator_(SAML_2.0_SSO)|SAMLAuthenticator]]. | ||
* '''SAML XML hardening''' — SAML XML processing no longer resolves external DTDs or stylesheets, and an IdP metadata URL must use http or https. See [[Authenticator#SAMLAuthenticator_(SAML_2.0_SSO)|SAMLAuthenticator]]. | |||
* ''' | * '''SSO redirect hardening''' — SSO redirects to the identity provider come only from the configured SSO settings or IdP metadata, and SAML RelayState is restricted. See [[Authenticator#OAuthAuthenticator_(OIDC_SSO)|OAuthAuthenticator]] and [[Authenticator#SAMLAuthenticator_(SAML_2.0_SSO)|SAMLAuthenticator]]. | ||
* ''' | * '''LDAP login input hardening''' — Login usernames are escaped when building LDAP bind and search queries. See [[Authenticator#Customizing_our_LDAP_Authenticator|LDAP Authenticator]]. | ||
* ''' | * '''Outbound URL fetch hardening''' — Outbound fetches allow only http and https URLs, and REST event hook and client licence URLs must resolve to publicly routable hosts. See [[Upgrading_Obsidian#Upgrading_to_7.1.0|Upgrading]] and [[Authenticator#SAMLAuthenticator_(SAML_2.0_SSO)|SAMLAuthenticator]]. | ||
* ''' | * '''SSO session cookie tracking''' — SSO sessions are tracked with cookies only. See [[Authenticator]]. | ||
* '''SSO session cookie tracking''' — See [[Authenticator]]. | * '''DBAuthenticator password hashing upgrade''' — DBAuthenticator stores passwords with a modern one-way hash, upgraded when a user signs in or changes a password. See [[Upgrading_Obsidian#Upgrading_to_7.1.0|Upgrading]] and [[Authenticator#DBAuthenticator|DBAuthenticator]]. | ||
* ''' | * '''Licence HTTPS trust hardening''' — <code>allowSelfSignedCert</code> is removed. A key server proxy using a private CA or self-signed certificate needs a truststore configured. See [[Upgrading_Obsidian#Upgrading_to_7.1.0|Upgrading]] and [[Key_Server_Proxy|Key Server Proxy]]. | ||
* ''' | * '''REST API login lockout for native accounts''' — Failed REST Basic authentication attempts count toward the maximum invalid attempts and can disable an account, as browser sign-in does. See [[Authenticator#DBAuthenticator|DBAuthenticator]]. | ||
* '''Mail JNDI session name hardening''' — See [[Upgrading_Obsidian#Upgrading_to_7.1.0|Upgrading]] and [[Advanced_Configuration|Advanced Configuration]]. | * '''Mail JNDI session name hardening''' — The JNDI Email Path must be a JNDI name, with an optional <code>java:</code> prefix. See [[Upgrading_Obsidian#Upgrading_to_7.1.0|Upgrading]] and [[Advanced_Configuration|Advanced Configuration]]. | ||
=== Bug Fixes === | === Bug Fixes === | ||
* '''Job Activity no longer repeats a one-time/chain priority message''' | * '''Job Activity no longer repeats a one-time/chain priority message''' | ||
* '''Linux embedded Tomcat systemd integration''' — See [[Linux_Service]]. | * '''Linux embedded Tomcat systemd integration''' — Fixed the installer's systemd integration for Embedded Tomcat on Linux, including when the step is offered, the profile used, and service status tracking. See [[Linux_Service|Linux Service]]. | ||
* '''SSO returns to the requested page''' — After OAuth/OIDC or SAML sign-in, and after re-authenticating from the session-expiry prompt, the UI returns to the page that was requested. | * '''SSO returns to the requested page''' — After OAuth/OIDC or SAML sign-in, and after re-authenticating from the session-expiry prompt, the UI returns to the page that was requested. | ||
* '''Bookmarked pages return after sign-in''' — Opening a bookmarked admin URL while signed out, then signing in, returns to that page. | * '''Bookmarked pages return after sign-in''' — Opening a bookmarked admin URL while signed out, then signing in, returns to that page. | ||
| Line 58: | Line 50: | ||
* '''extra.log4j2.properties.N''' — Extra logging lines are replaced by the installer log4j2 XML editor. See [[Installation_Guide#Log_path|Log path]]. | * '''extra.log4j2.properties.N''' — Extra logging lines are replaced by the installer log4j2 XML editor. See [[Installation_Guide#Log_path|Log path]]. | ||
* '''Standalone SIGTERM handler removed''' — See [[Advanced_Configuration|Advanced Configuration]] (standalone shutdown). | * '''Standalone SIGTERM handler removed''' — The optional JVM SIGTERM handler (<code>signalHandlerActiveForScheduler</code>) for the Standalone Runtime is removed. See [[Advanced_Configuration|Advanced Configuration]] (standalone shutdown). | ||
== Obsidian 7.0.2 == | == Obsidian 7.0.2 == | ||
Latest revision as of 03:07, 31 October 2026
Please review our Upgrade Instructions.
Read about our Planned Releases.
Looking for old release notes? See Release Notes - Older Releases.
Obsidian 7.1.0
To Be Released November 2026
Features / Enhancements
- Updated third-party libraries — Bundled third-party libraries were updated to current releases. See Dependent Libraries for the current list.
- REST API Postman collection — A Postman collection and sample environment for the REST API are included in the release zip and the Documentation pack. See REST API.
- JavaScript scripting engine — Scripting Jobs bundle OpenJDK Nashorn so JavaScript jobs run on JDK 15 and later. The installer's Script Libraries step has a JavaScript option, cleared by default. See Scripting Jobs.
- Additional Maven dependencies at install — An optional installer step adds extra Maven libraries, with their transitive dependencies, to the scheduler WAR and Standalone Runtime from a file or pasted list. See Additional Maven dependencies.
- Host Status version — Host Status shows each host's Obsidian version and displays a banner when host versions differ from the web UI or from each other. See Admin Host Status.
- Single mail implementation jar — Both JavaMail implementations ship in one
jdk.jarandobsidian.jar, and the installer's Email Implementation step selects which one is used. See Advanced Configuration. - Linux systemd services — On Linux, the installer can offer systemd service files for Embedded Tomcat and the Standalone Runtime. The services are not enabled or started automatically. See Linux Service.
- Log path per installer artifact — When more than one of the WAR, Admin WAR, and Standalone Runtime is selected, each can have its own optional log path. See Log path.
- Log4j2 configuration is XML — The installer generates log4j2 as XML, which you can edit on the Log4j2 XML screen or supply as a sidecar file. See Log path.
Security Enhancements
- Updated UI JavaScript packages — Many UI npm packages were updated for known security vulnerabilities.
- Standalone scheduler shutdown hardening — The Standalone Runtime stop listener now requires a shared secret and binds to loopback by default. See Advanced Configuration (standalone stop listener).
- OAuth/SAML response hardening — OAuth and SAML endpoints set explicit content types, and post-login return URLs are restricted to relative or same-host targets. See OAuthAuthenticator and SAMLAuthenticator.
- SAML XML hardening — SAML XML processing no longer resolves external DTDs or stylesheets, and an IdP metadata URL must use http or https. See SAMLAuthenticator.
- SSO redirect hardening — SSO redirects to the identity provider come only from the configured SSO settings or IdP metadata, and SAML RelayState is restricted. See OAuthAuthenticator and SAMLAuthenticator.
- LDAP login input hardening — Login usernames are escaped when building LDAP bind and search queries. See LDAP Authenticator.
- Outbound URL fetch hardening — Outbound fetches allow only http and https URLs, and REST event hook and client licence URLs must resolve to publicly routable hosts. See Upgrading and SAMLAuthenticator.
- SSO session cookie tracking — SSO sessions are tracked with cookies only. See Authenticator.
- DBAuthenticator password hashing upgrade — DBAuthenticator stores passwords with a modern one-way hash, upgraded when a user signs in or changes a password. See Upgrading and DBAuthenticator.
- Licence HTTPS trust hardening —
allowSelfSignedCertis removed. A key server proxy using a private CA or self-signed certificate needs a truststore configured. See Upgrading and Key Server Proxy. - REST API login lockout for native accounts — Failed REST Basic authentication attempts count toward the maximum invalid attempts and can disable an account, as browser sign-in does. See DBAuthenticator.
- Mail JNDI session name hardening — The JNDI Email Path must be a JNDI name, with an optional
java:prefix. See Upgrading and Advanced Configuration.
Bug Fixes
- Job Activity no longer repeats a one-time/chain priority message
- Linux embedded Tomcat systemd integration — Fixed the installer's systemd integration for Embedded Tomcat on Linux, including when the step is offered, the profile used, and service status tracking. See Linux Service.
- SSO returns to the requested page — After OAuth/OIDC or SAML sign-in, and after re-authenticating from the session-expiry prompt, the UI returns to the page that was requested.
- Bookmarked pages return after sign-in — Opening a bookmarked admin URL while signed out, then signing in, returns to that page.
- Session timeout shows the login screen — After the session expires, Obsidian shows the login screen. Multi-factor authentication is requested only after username and password are submitted.
- Host Status badge refreshes after sign-in — After a session timeout, signing in again updates the Host Status nav badge from a live host list.
Removals
- extra.log4j2.properties.N — Extra logging lines are replaced by the installer log4j2 XML editor. See Log path.
- Standalone SIGTERM handler removed — The optional JVM SIGTERM handler (
signalHandlerActiveForScheduler) for the Standalone Runtime is removed. See Advanced Configuration (standalone shutdown).
Obsidian 7.0.2
Released August 2026
Bug Fixes
- Scheduler startup on JDK 17 — Fixed an issue where JDK 17 required Unsafe for GSON deserialization. Unsafe is globally disabled now.
- Startup / shutdown job modes on Postgres and SQL Server — Job column for modes was too short for some mode values.
Obsidian 7.0.1
Released August 2026
Bug Fixes
- Fixed site and hardware-linked licence verification on Obsidian 7.0.0. Workaround for 7.0.0 available on request.
Obsidian 7.0.0
Released July 2026
Features / Enhancements
- OAuth 2.0 / OIDC Single Sign-On — Obsidian now supports OAuth 2.0 / OIDC SSO authentication via OAuthAuthenticator. Configure any OIDC-compliant identity provider (Keycloak, Microsoft Entra ID, Okta, Auth0, or Generic OIDC) as the login provider. See OAuth/OIDC Authentication Properties for full configuration details.
- Bearer JWT authentication for the REST API — REST clients can now authenticate using a signed JWT access token in the Authorization: Bearer header. See OAuth/OIDC Authentication Properties for configuration.
- Embedded Tomcat quick start — Evaluation and local runs use an Apache Tomcat 10.1.x embedded runtime (Jakarta Servlet). The bundled sample is h2-tomcat-quick-start.xml. webObsidian scripts start/stop embedded Tomcat for scheduler or admin-only profiles — see Deployment options and Starting Obsidian with embedded Tomcat.
- On Linux, embedded Tomcat packs also install optional user-level systemd and desktop integration — see the installer option and Running Obsidian as a Linux user service.
- Global parameter autocomplete and tooltips — While editing a job, typing {{ in a parameter value opens suggestions for global parameter names (subject to visibility settings). On job view, hover over values containing Name to see resolved global values when your user's permissions allow. Administration screens for defining global parameters are unchanged. See Advanced Configuration for visibility settings.
- Install-time dependency resolution — The published installer download does not embed public open-source JARs. Libraries are fetched (or read from a pre-staged cache) when you run the installer. See Offline install for air-gapped preparation steps.
- Installer upgrade (IzPack 5) — Obsidian 7.0.0 ships an IzPack 5-based installer. GUI and headless installs behave as in Obsidian 6 for standard flows. Customers with saved Obsidian 6 automated install XML must run the migrate helper included in the download before headless install. See Upgrading Obsidian.
- Modular Groovy and Flexmark libraries — Obsidian no longer ships apache-groovy-all-4.0.24.jar or flexmark-util-0.62.2.jar uber archives. Scripting and UI documentation rendering use the modular JAR sets documented in Dependent Libraries.
Removals
- Remember Me login option removed — The Remember Me checkbox and associated session-cookie mechanism have been removed. The USER_COOKIE table and allowRememberMe system parameter are removed automatically during the upgrade to 7.0.0; no operator action is required.
Bug Fixes
- User logout - Fixed an issue where users were not fully logged out in certain session states.
- Job edit screen accessible to users with no roles — Users with no assigned roles could previously access the job edit screen but not make changes; this has been fixed.
- Firefox UI icons — Fixed icons not rendering correctly in Firefox.
- Jakarta emails sent with both text and HTML would drop HTML portion; this has been fixed.
Obsidian 6.4.0
Released December 2025
Enhancements
- New Execution Statistics Job and built in UI and Embedded API and REST API
Bug Fixes
- Fixed issue preventing job deletion when resubmissions of failed executions existed. Bug existed in UI and APIs.
- Fixed UI styling issue for job deletion where checkbox label did not appear.
Obsidian 6.3.3
Released November 2025
Enhancements
- LDAPAuthenticator supports configurable check user active override - com.carfey.suite.security.LdapAuthenticator.checkActiveAttribute
- LDAPAuthenticator.isUserActive(DirContext,String) visibility increased to protected to allow for functionality override in subclasses.
Bug Fixes
- Correct LdapAuthenticator case with delimited configuration where active check wasn't applied.
- LDAPAuthenticator.isUserActive(DirContext,String) javadoc added for isUserActive fully detailing the implementation.
Obsidian 6.3.2
Released October 2025
Enhancements
- Notification failures now trigger Dispatch category Error level event on first failure. For use in log alerts and Event Hooks.
Bug Fixes
- Notification failures no longer log on every failure reducing chatty failure logs.
- No-arg constructors added to multiple JSON serializable candidate POJOs missing them. Addresses GSON's workaround use of sun.misc.Unsafe.
Obsidian 6.3.1
Released August 2025
Bug Fixes
- Fix failure response codes on REST health endpoint
- Fix automatic upgrade issue from 6.1.0 to any of 6.2.0, 6.2.1, 6.3.0
- Fix auth issue when MFA is enabled that allows REST access when account has been locked out due to MFA not being setup. Contact us if you need workaround details for earlier versions.
- Fix native auth issue that allows REST access when account has been flagged as inactive.
Obsidian 6.3.0
Released July 2025
Features / Enhancements
- Cron day of month expansion for day of week proximity using ~
- Annotation based job and chain configuration initialization
- Health endpoint with details for Job Queuer and Job Spawner - REST API or Embedded API by hostname or by host id
- JDBC URL construction from parts host/port/databaseName/dbType/oracleSid
Obsidian 6.2.1
Released June 2025
Bug Fixes
- Certain recoveries greater than 24 hours using new day of month proximity patterns introduced in 6.2.0 would result in no jobs spawning.
- Migrations targeting 6.0.0 and greater that start earlier than 5.0.0 skip the 5.0.0 migration. Migrating to any 5.x version first and then to 6.0.0 or later works around this issue.
Obsidian 6.2.0
Released May 2025
Features / Enhancements
- Cron day of month expansion for day of week proximity using < > ≥ ≤
- Cron day of month expansion for weekday proximity using < > ≥ ≤
- Global Parameters reference in job edit page support mouseover/title display of actual value when permissions allow
- Host time displayed in hosts status in UI
- Runtime Preview optimizations for large date ranges in both UI and APIs.
Bug Fixes
- Combination of table prefix, sorting by clob column and Oracle metadata load failure no longer results in sql error. This occurred in the UI when viewing raw job history results and in API calls for job runtime results.
Obsidian 6.1.1
Released March 2025
Features / Enhancements
- Authenticator supports optional
authenticateREST()method.
Bug Fixes
- Native authentication REST logins do not apply 'last login' timestamps. Avoids noisy error that was appearing in logs.
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.
- Native authentication last login datetime displayed on list user screen.
- 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.
