Releases: perforce/helix-authentication-extension
Releases · perforce/helix-authentication-extension
2024.2
New functionality
- No new features in this release.
2024.1
Bugs fixed
- Perforce user with 'ldap+2fa' was mistakenly given a login URL.
- Extension could not connect to the service in certain circumstances that involves a complex network setup. Added Resolve-Host setting to provide a work-around in those scenarios.
2023.2
Bugs fixed
- Configure script now captures all existing settings when upgrading an existing extension installation.
2023.1
New functionality
- Add configurable Service-Down-URL to which the extension will direct the user in the event that the authentication service is failing.
2022.2
Bug fixes
- Configure script will build extension before removing existing extension, avoiding issue with older p4 client failing to build the extension.
2022.1
Bug fixes
- A cryptographically signed build of the extension will be provided via GitHub, avoiding the need to allow unsigned extensions.
- If the extension setting Service-URL is missing from the global configuration, the extension will fail in a manner that still permits database-password accounts to authenticate.
2021.2
Improvements
- Allow changing the TLS certificate file paths.
2021.1
Bug fixes
- Configure script now reads extension configuration correctly.
- Extension correctly distinquishes P4V from P4VS during login.
2020.2
Bug fixes
- Add options "sso-users" and "sso-groups" to define Perforce users and groups that must use the SSO authentication mechanism.
2020.1 patch 1
Only minor changes, tagged for parity with the helix-authentication-service 2020.1.1 release.