Orchestrator build release notes
Orchestrator build release notes
For older release notes, see the release notes archive.
v0.49.0
2024-11-19
- Multiple ConsumerServiceURLs per SAML app are now supported.
v0.48.1
2024-11-15
- Orchestrator uses a POST binding when available on SAML login.
v0.48.0
2024-11-15
- You can now load Windows Store certs using Hashicorp Vault.
v0.47.0
2024-11-13
- Log level settings are reloadable.
v0.46.0
2024-11-13
- ECDH certs can now be loaded from Windows Cert Store.
v0.45.0
2024-11-08
- CRL revocation is now supported for TLS. See docs.
v0.44.5
2024-11-08
- Resolved issue where cached SAML requests were failing to be unmarshaled due to the POST binding not supporting compressed requests.
v0.44.2
2024-11-04
- Service extensions can now be used in conjunction with attribute providers for SAML and OIDC.
v0.44.1
2024-10-31
- SAML apps now successfully log errors if attempts to load attributes are not found or not defined.
v0.44.0
2024-10-30
- Online Certificate Status Protocol (OCSP) is now supported to allow clients and servers to check the revocation status of their peer’s certificate. See docs.
v0.43.0
2024-10-29
- An error logger has been added to the HTTP server to make TLS handshake errors in Windows visible in the event viewer.
v0.42.0
2024-10-25
- Only tokens issues with the
openid
scope can be used at theuserinfo
endpoint.
v0.41.0
2024-10-25
- Support for mTLS cert authentication on HashiCorp Vault for Linux.
v0.40.0
2024-10-22
- Minor internal improvements
v0.39.0
2024-10-22
- As part of Orchestrator on Ubuntu, Debian artifacts are now included in Maverics releases.
- The Orchestrator health configuration is now reloadable, facilitating changes in the UI being pushed down to Orchestrator without requiring a restart.
v0.38.0
2024-10-18
- Minor internal improvements
v0.37.0
2024-10-17
- Improvements to the generic SAML health check HTTP client.
v0.36.0
2024-10-17
- TLS Unmarshalling has been reworked to simplify and combine multiple constructors.
v0.35.0
2024-10-17
- OIDC Provider:
sub
andclient_id
claims can now be overwritten via service extension. ID token generation has also been updated to no longer include theclient_id
claim by default.
v0.33.0
2024-10-15
- Debian package installer changes.
- Consolidate connector ‘Login’ logic where duplicated: In a handful of connectors,
Login
logic was duplicated between the login requester and the connector object itself. In other connectors, the connectorLogin
is a thin wrapper around theloginRequester
. This PR consolidates logic in the remaining connectors
v0.32.0
2024-10-10
- Debian package installer changes.
- OIDC Provider User Info Handler: The userinfo handler now uses the claim mapping on the client to build the response. A token cache entry will need to have a clear mapping to the
client_id
associated with the token.
v0.31.0
2024-10-09
- [OIDC Provider] Add association from token cache to userinfo cache - #2592
v0.30.0
2024-10-07
- [OIDC Provider] Store userinfo data only once - #2589
v0.29.1
2024-10-02
- [Connectors] Infer correct protocol binding from SAML metadata - #2588
v0.29.0
2024-10-01
- Expose ‘jose.ContentType’ in service extensions - #2587
v0.28.0
2024-10-01
- [Connectors] Add support for login hint via subject in PingFed SAML - #2586