Main-20250430-rc3

This is a bugfix and feature pre-release in preparation for next actual release:

• Fix routing of migcert reset password requests (PR #204)
• Begin moving scripts like edpickle to new bin dir for clarity (PR #197)
• Add account renewal button for local accounts on Account page (PR #196)
• Fix migrid init sftpsubsys status (PR #221)
• Switch to is_*() methods across Thread and Thread.Event to address errors in issue #224
• Address security issues in CamanJS dependencies used if image previews are enabled (PR #226)
• Adjust service auth policy to avoid giving away information about user non-/existence (PR #209)
• Fix account page errors for legacy account entries without complete peers data (PR #227)
• Fix a leftover string expansion issue on Accounts page in python2 deployments (PR #230)
• Proper session clean up during logout including project + 2FA with extoidc auth (Issue #222 / PR #223)
• Fix GDP projects with space in name not accessible through SFTP (subsys) (Issue #234 / PR #233)
• Command format adjustment for better readability as suggested in issue #235

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Stable-20250430-rc3

This is a bugfix and feature pre-release in preparation for next actual release:

• Fix routing of migcert reset password requests (PR #204)
• Begin moving scripts like edpickle to new bin dir for clarity (PR #197)
• Add account renewal button for local accounts on Account page (PR #196)
• Fix migrid init sftpsubsys status (PR #221)
• Switch to is_*() methods across Thread and Thread.Event to address errors in issue #224
• Address security issues in CamanJS dependencies used if image previews are enabled (PR #226)
• Adjust service auth policy to avoid giving away information about user non-/existence (PR #209)
• Fix account page errors for legacy account entries without complete peers data (PR #227)
• Fix a leftover string expansion issue on Accounts page in python2 deployments (PR #230)
• Proper session clean up during logout including project + 2FA with extoidc auth (Issue #222 / PR #223)
• Fix GDP projects with space in name not accessible through SFTP (subsys) (Issue #234 / PR #233)
• Command format adjustment for better readability as suggested in issue #235

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Next-20250401-rc2

This is a bugfix and feature pre-release in preparation for next actual release:

• Change details will be added here in time for the actual release

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Main-20250401-rc2

This is a bugfix and feature pre-release in preparation for next actual release:

• Change details will be added here in time for the actual release

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Stable-20250401-rc2

This is a bugfix and feature pre-release in preparation for next actual release:

• Change details will be added here in time for the actual release

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Next-20250319-rc1

This is a bugfix and feature pre-release in preparation for next actual release:

• Change details will be added here in time for the actual release

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Main-20250319-rc1

This is a bugfix and feature pre-release in preparation for next actual release:

• Change details will be added here in time for the actual release

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Stable-20250319-rc1

This is a bugfix and feature pre-release in preparation for next actual release:

• Change details will be added here in time for the actual release

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Next-20250210

This is a bugfix and feature release:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173+179+180)
• Prevent external users changing ID fields during semi-automatic renew with authentication (PR174)
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Switched unit testing to consistent docker containerization for py2+3 but still with native support (PR134)
• Fix a corner-case bug with exceptions in output handling (PR178)
• Clean up old unused native dev account code obsoleted by containerized deployments (PR185)
• Fix crashes in the PAM module on Rocky/RHEL 8+ in the handling of repeated sftpsubsys login failures (PR188+189)
• Helper to refresh old accounts in relation to switch from OpenID 2.0 to OpenID Connect auth provider (PR181)
• Integration of built-in status page as standalone virtual host alias like https://status.erda.dk (PR192)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Main-20250210

This is a bugfix and feature release:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173+179+180)
• Prevent external users changing ID fields during semi-automatic renew with authentication (PR174)
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Switched unit testing to consistent docker containerization for py2+3 but still with native support (PR134)
• Fix a corner-case bug with exceptions in output handling (PR178)
• Clean up old unused native dev account code obsoleted by containerized deployments (PR185)
• Fix crashes in the PAM module on Rocky/RHEL 8+ in the handling of repeated sftpsubsys login failures (PR188+189)
• Helper to refresh old accounts in relation to switch from OpenID 2.0 to OpenID Connect auth provider (PR181)
• Integration of built-in status page as standalone virtual host alias like https://status.erda.dk (PR192)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.