Releases: openziti/zrok
v2.0.1
CHANGELOG
FEATURE: Added several new admin API endpoints for interfacing with additional management controls: finding limit classes by label, finding applied/applying/removing limit classes from accounts, getting/setting skip interstitial status for an account (#1210)
CHANGE: Removed the legacy admin /grants endpoint. Its prior synchronization behavior is now replaced by the new skip interstitial grant management endpoints. (#726)
CHANGE: Applying limit classes now validates requested assignments to prevent conflicting effective limit class combinations on an account (#726)
FIX: Escaped proxyUi output by switching to html/template and removed reflected refreshInterval values from github oauth error pages.
FIX: Users could get into a state where an allocated name returns a 500 error; this happened by various combinations of abnormal share termination, or deleting a name from underneath a live share... both resulted in bad frontend mappings that prevented proper share operation. The zrok2 delete name now refuses to delete names with an active share (zrok2 delete share first). The zrok2 create name now includes "healing" functionality that removes extraneous frontend mapping rows for the newly created namespace. Users can zrok2 delete name and zrok2 create name to fix any old issues around this. (#1219)
FIX: Configurable upper limit on the number of cookie stripes allowed for the OAuth session cookie; includes hard limit on upper number of stripes at 32. Defaults to 10. (#1217)
FEATURE: New zrok2 delete access subcommand that allows end users to clean up stale access frontends from the command line.
FIX: Security hardening for the /unaccess endpoint.
FIX: Always return success on reset password request, even if account not found... unless there was actually an error.
v2.0.0
CHANGELOG
FEATURE: Major changes to how "unique names" and "reserved sharing" work. See the zrok v2 Migration Guide for details. Reserved sharing, including the zrok reserve, zrok release and zrok share reserved commands have been removed. Namespaces and reserved names replace these concepts in a much more powerful, flexible way which can accomplish what reserved sharing did in a much better way. (#726)
CHANGE: Binary renamed from zrok to zrok2. This allows zrok v1 and v2 to coexist on the same system without conflicts. All command invocations now use zrok2 (e.g., zrok2 enable, zrok2 share public). (#1124)
CHANGE: Environment directory changed from ~/.zrok to ~/.zrok2. This provides complete isolation between v1 and v2 environments. Users running zrok2 enable will create a new environment in ~/.zrok2; existing ~/.zrok environments are not affected. (#1124)
CHANGE: Environment variables renamed from ZROK_* to ZROK2_*. All environment variables now use the ZROK2_ prefix (e.g., ZROK2_API_ENDPOINT, ZROK2_ADMIN_TOKEN, ZROK2_ENABLE_TOKEN). This ensures v1 and v2 environment configurations do not interfere with each other. (#1124)
CHANGE: Linux packages renamed to zrok2, zrok2-agent. The agent's systemd user service file is renamed to zrok2-agent.service. Configuration directory changed to /etc/zrok2. (#1124)
CHANGE: Removed env_v0_3 compatibility layer. Since zrok2 uses ~/.zrok2 exclusively and will never touch ~/.zrok, the v0.3 environment migration code has been removed. The update infrastructure remains for future version upgrades.
FEATURE: zrok2 share private now includes a --share-token flag, which allows a user to create a vanity token for private shares. Now that reserved sharing has been replaced with namespaces, the --share-token flag allows private sharing to retain custom, persistent share token names. (#1070)
FEATURE: zrok2 modify name command available to "upgrade" an ephemeral share name to a reserved share name. If you share something ephemerally and later decide that you want to persist that name for future use you can just zrok2 modify name -r that name and retain it indefinitely (or conversely zrok2 modify name -r=false to schedule a reserved name to be released when an associated share is terminated). (#1066)
FEATURE: New zrok2 list names, zrok2 list namespaces, zrok2 list environments, zrok2 list shares, and zrok2 list accesses commands available to query the environments, shares, and accesses contained in the user's account; supports filtering on activity, accesses, shares, descriptions, host, ip address, and other relevant search criteria. By default outputs human-readable tabular output, but has a --json option to emit the values as JSON. (#1107)
FEATURE: New zrok2 delete environment command that allows for deleting environments other than the current enabled environment. Use zrok2 list environments --idle to find idle environments and remove them using zrok2 delete environment. (#1107)
FEATURE: New zrok2 access dynamicProxy which is designed to work with the new namespaces/names functionality. Rather than parsing the Host header and trying to extract a share token, the new dynamicProxy receives mapping updates from the zrok controller, allowing it to support any kind of mapped name. See the zrok dynamicProxy Guide for details on setting up the new frontend. zrok2 access public remains available for legacy-style setups. (#1041)
FEATURE: The zrok Agent now includes significantly improved handling for subordinate processes in error states. Errors encountered during agent reloading and also during active runtime are retried using an exponential falloff approach. Errored accesses or shares are given transient err_XXXX tokens, which can be used to manage (release) these processes. (#1000)
FEATURE: The zrok Agent has been updated for v2 name selections. Now that "reserved shares" have been replaced with reserved names, the zrok Agent will automatically restart any share which contains a name selection with a reserved name. The Agent continues to automatically manage zrok2 access private processes as always.
FEATURE: zrok2 overview now includes a human-readable default output, that formats the details of your zrok account in an easy-to-understand format. The classic JSON output is still available using the --json flag. (#1064)
FEATURE: zrok2 admin migrate now supports a --down <n> flag, which allows for reverse-migration by a specified number of migrations
CHANGE: The root package path was migrated from github.com/openziti/zrok to github.com/openziti/zrok/v2 to accomodate golang v2+ package naming semantics.
CHANGE: zrok2 status now shows EnvZId instead of Ziti Identity in output. (#1107)
CHANGE: defaultFrontend configuration replaced with new defaultNamespace, which provides the logical equivalent of the old name-handling configuration (#1065)
CHANGE: zrok2 admin create frontend, zrok2 admin update frontend now include a new --dynamic flag which allows setting/changing the value of the dynamic property in the frontend. Setting dynamic is required when configuring a dynamicProxy frontend. zrok2 admin list frontends now displays the dynamic value of the frontends in the system. zrok2 admin list frontends includes a new --extra flag to display the additional/v1 properties maintained for frontends. (#1096)
CHANGE: Completely overhauled the core ziti automation logic. The legacy controller/zrokEdgeSdk package has been replaced with a much more streamlined, clearer package controller/automation. This makes comprehending the controller code a lot simpler. (#1054)
CHANGE: Updated github.com/openziti/sdk-golang to v1.2.4.
CHANGE: All logging migrated from githhub.com/michaelquigley/pfxlog and github.com/sirupsen/logrus to github.com/michaelquigley/df/dl and log/slog. Use environment variable DL_USE_JSON=true to force JSON output. Use DL_USE_COLOR to force colorized output. (#1078)
FIX: Updated the unique constraint on the accounts.email column to only be unique when is not deleted. This only fixes PostgreSQL databases; fixing SQLite databases effectively requires rebuilding the entire database, see the comment in the issue for details. (#1109)
FEATURE: Added configuration option for OIDC authentication prompts.
FEATURE: New names>disable_share_token_profanity_check and names>disable_namespace_name_profanity_check configuration options to disable profanity checking for share tokens and namespace names. (#1152)
FEATURE: zrok2 admin update password; adminstrative password change function (#1129)
FIX: Improved ipv6 address parsing in realRemoteAddress in the controller package.
v2.0.0-rc8
CHANGELOG
This is a pre-release version of zrok v2.0.0. Not all recipes, platforms and distributions have been updated yet.
FEATURE: Major changes to how "unique names" and "reserved sharing" work. See the zrok v2 Migration Guide for details. Reserved sharing, including the zrok reserve, zrok release and zrok share reserved commands have been removed. Namespaces and reserved names replace these concepts in a much more powerful, flexible way which can accomplish what reserved sharing did in a much better way. (#726)
CHANGE: Binary renamed from zrok to zrok2. This allows zrok v1 and v2 to coexist on the same system without conflicts. All command invocations now use zrok2 (e.g., zrok2 enable, zrok2 share public). (#1124)
CHANGE: Environment directory changed from ~/.zrok to ~/.zrok2. This provides complete isolation between v1 and v2 environments. Users running zrok2 enable will create a new environment in ~/.zrok2; existing ~/.zrok environments are not affected. (#1124)
CHANGE: Environment variables renamed from ZROK_* to ZROK2_*. All environment variables now use the ZROK2_ prefix (e.g., ZROK2_API_ENDPOINT, ZROK2_ADMIN_TOKEN, ZROK2_ENABLE_TOKEN). This ensures v1 and v2 environment configurations do not interfere with each other. (#1124)
CHANGE: Linux packages renamed to zrok2, zrok2-agent. The agent's systemd user service file is renamed to zrok2-agent.service. Configuration directory changed to /etc/zrok2. (#1124)
CHANGE: Removed env_v0_3 compatibility layer. Since zrok2 uses ~/.zrok2 exclusively and will never touch ~/.zrok, the v0.3 environment migration code has been removed. The update infrastructure remains for future version upgrades.
FEATURE: zrok2 share private now includes a --share-token flag, which allows a user to create a vanity token for private shares. Now that reserved sharing has been replaced with namespaces, the --share-token flag allows private sharing to retain custom, persistent share token names. (#1070)
FEATURE: zrok2 modify name command available to "upgrade" an ephemeral share name to a reserved share name. If you share something ephemerally and later decide that you want to persist that name for future use you can just zrok2 modify name -r that name and retain it indefinitely (or conversely zrok2 modify name -r=false to schedule a reserved name to be released when an associated share is terminated). (#1066)
FEATURE: New zrok2 list names, zrok2 list namespaces, zrok2 list environments, zrok2 list shares, and zrok2 list accesses commands available to query the environments, shares, and accesses contained in the user's account; supports filtering on activity, accesses, shares, descriptions, host, ip address, and other relevant search criteria. By default outputs human-readable tabular output, but has a --json option to emit the values as JSON. (#1107)
FEATURE: New zrok2 delete environment command that allows for deleting environments other than the current enabled environment. Use zrok2 list environments --idle to find idle environments and remove them using zrok2 delete environment. (#1107)
FEATURE: New zrok2 access dynamicProxy which is designed to work with the new namespaces/names functionality. Rather than parsing the Host header and trying to extract a share token, the new dynamicProxy receives mapping updates from the zrok controller, allowing it to support any kind of mapped name. See the zrok dynamicProxy Guide for details on setting up the new frontend. zrok2 access public remains available for legacy-style setups. (#1041)
FEATURE: The zrok Agent now includes significantly improved handling for subordinate processes in error states. Errors encountered during agent reloading and also during active runtime are retried using an exponential falloff approach. Errored accesses or shares are given transient err_XXXX tokens, which can be used to manage (release) these processes. (#1000)
FEATURE: The zrok Agent has been updated for v2 name selections. Now that "reserved shares" have been replaced with reserved names, the zrok Agent will automatically restart any share which contains a name selection with a reserved name. The Agent continues to automatically manage zrok2 access private processes as always.
FEATURE: zrok2 overview now includes a human-readable default output, that formats the details of your zrok account in an easy-to-understand format. The classic JSON output is still available using the --json flag. (#1064)
FEATURE: zrok2 admin migrate now supports a --down <n> flag, which allows for reverse-migration by a specified number of migrations
CHANGE: The root package path was migrated from github.com/openziti/zrok to github.com/openziti/zrok/v2 to accomodate golang v2+ package naming semantics.
CHANGE: zrok2 status now shows EnvZId instead of Ziti Identity in output. (#1107)
CHANGE: defaultFrontend configuration replaced with new defaultNamespace, which provides the logical equivalent of the old name-handling configuration (#1065)
CHANGE: zrok2 admin create frontend, zrok2 admin update frontend now include a new --dynamic flag which allows setting/changing the value of the dynamic property in the frontend. Setting dynamic is required when configuring a dynamicProxy frontend. zrok2 admin list frontends now displays the dynamic value of the frontends in the system. zrok2 admin list frontends includes a new --extra flag to display the additional/v1 properties maintained for frontends. (#1096)
CHANGE: Completely overhauled the core ziti automation logic. The legacy controller/zrokEdgeSdk package has been replaced with a much more streamlined, clearer package controller/automation. This makes comprehending the controller code a lot simpler. (#1054)
CHANGE: Updated github.com/openziti/sdk-golang to v1.2.4.
CHANGE: All logging migrated from githhub.com/michaelquigley/pfxlog and github.com/sirupsen/logrus to github.com/michaelquigley/df/dl and log/slog. Use environment variable DL_USE_JSON=true to force JSON output. Use DL_USE_COLOR to force colorized output. (#1078)
FIX: Updated the unique constraint on the accounts.email column to only be unique when is not deleted. This only fixes PostgreSQL databases; fixing SQLite databases effectively requires rebuilding the entire database, see the comment in the issue for details. (#1109)
FEATURE: Added configuration option for OIDC authentication prompts.
FEATURE: New names>disable_share_token_profanity_check and names>disable_namespace_name_profanity_check configuration options to disable profanity checking for share tokens and namespace names. (#1152)
FEATURE: zrok2 admin update password; adminstrative password change function (#1129)
FIX: Improved ipv6 address parsing in realRemoteAddress in the controller package.
v2.0.0-rc7
CHANGELOG
This is a pre-release version of zrok v2.0.0. Not all recipes, platforms and distributions have been updated yet.
FEATURE: Major changes to how "unique names" and "reserved sharing" work. See the zrok v2 Migration Guide for details. Reserved sharing, including the zrok reserve, zrok release and zrok share reserved commands have been removed. Namespaces and reserved names replace these concepts in a much more powerful, flexible way which can accomplish what reserved sharing did in a much better way. (#726)
CHANGE: Binary renamed from zrok to zrok2. This allows zrok v1 and v2 to coexist on the same system without conflicts. All command invocations now use zrok2 (e.g., zrok2 enable, zrok2 share public). (#1124)
CHANGE: Environment directory changed from ~/.zrok to ~/.zrok2. This provides complete isolation between v1 and v2 environments. Users running zrok2 enable will create a new environment in ~/.zrok2; existing ~/.zrok environments are not affected. (#1124)
CHANGE: Environment variables renamed from ZROK_* to ZROK2_*. All environment variables now use the ZROK2_ prefix (e.g., ZROK2_API_ENDPOINT, ZROK2_ADMIN_TOKEN, ZROK2_ENABLE_TOKEN). This ensures v1 and v2 environment configurations do not interfere with each other. (#1124)
CHANGE: Linux packages renamed to zrok2, zrok2-agent. The agent's systemd user service file is renamed to zrok2-agent.service. Configuration directory changed to /etc/zrok2. (#1124)
CHANGE: Removed env_v0_3 compatibility layer. Since zrok2 uses ~/.zrok2 exclusively and will never touch ~/.zrok, the v0.3 environment migration code has been removed. The update infrastructure remains for future version upgrades.
FEATURE: zrok2 share private now includes a --share-token flag, which allows a user to create a vanity token for private shares. Now that reserved sharing has been replaced with namespaces, the --share-token flag allows private sharing to retain custom, persistent share token names. (#1070)
FEATURE: zrok2 modify name command available to "upgrade" an ephemeral share name to a reserved share name. If you share something ephemerally and later decide that you want to persist that name for future use you can just zrok2 modify name -r that name and retain it indefinitely (or conversely zrok2 modify name -r=false to schedule a reserved name to be released when an associated share is terminated). (#1066)
FEATURE: New zrok2 list names, zrok2 list namespaces, zrok2 list environments, zrok2 list shares, and zrok2 list accesses commands available to query the environments, shares, and accesses contained in the user's account; supports filtering on activity, accesses, shares, descriptions, host, ip address, and other relevant search criteria. By default outputs human-readable tabular output, but has a --json option to emit the values as JSON. (#1107)
FEATURE: New zrok2 delete environment command that allows for deleting environments other than the current enabled environment. Use zrok2 list environments --idle to find idle environments and remove them using zrok2 delete environment. (#1107)
FEATURE: New zrok2 access dynamicProxy which is designed to work with the new namespaces/names functionality. Rather than parsing the Host header and trying to extract a share token, the new dynamicProxy receives mapping updates from the zrok controller, allowing it to support any kind of mapped name. See the zrok dynamicProxy Guide for details on setting up the new frontend. zrok2 access public remains available for legacy-style setups. (#1041)
FEATURE: The zrok Agent now includes significantly improved handling for subordinate processes in error states. Errors encountered during agent reloading and also during active runtime are retried using an exponential falloff approach. Errored accesses or shares are given transient err_XXXX tokens, which can be used to manage (release) these processes. (#1000)
FEATURE: The zrok Agent has been updated for v2 name selections. Now that "reserved shares" have been replaced with reserved names, the zrok Agent will automatically restart any share which contains a name selection with a reserved name. The Agent continues to automatically manage zrok2 access private processes as always.
FEATURE: zrok2 overview now includes a human-readable default output, that formats the details of your zrok account in an easy-to-understand format. The classic JSON output is still available using the --json flag. (#1064)
FEATURE: zrok2 admin migrate now supports a --down <n> flag, which allows for reverse-migration by a specified number of migrations
CHANGE: The root package path was migrated from github.com/openziti/zrok to github.com/openziti/zrok/v2 to accomodate golang v2+ package naming semantics.
CHANGE: zrok2 status now shows EnvZId instead of Ziti Identity in output. (#1107)
CHANGE: defaultFrontend configuration replaced with new defaultNamespace, which provides the logical equivalent of the old name-handling configuration (#1065)
CHANGE: zrok2 admin create frontend, zrok2 admin update frontend now include a new --dynamic flag which allows setting/changing the value of the dynamic property in the frontend. Setting dynamic is required when configuring a dynamicProxy frontend. zrok2 admin list frontends now displays the dynamic value of the frontends in the system. zrok2 admin list frontends includes a new --extra flag to display the additional/v1 properties maintained for frontends. (#1096)
CHANGE: Completely overhauled the core ziti automation logic. The legacy controller/zrokEdgeSdk package has been replaced with a much more streamlined, clearer package controller/automation. This makes comprehending the controller code a lot simpler. (#1054)
CHANGE: Updated github.com/openziti/sdk-golang to v1.2.4.
CHANGE: All logging migrated from githhub.com/michaelquigley/pfxlog and github.com/sirupsen/logrus to github.com/michaelquigley/df/dl and log/slog. Use environment variable DL_USE_JSON=true to force JSON output. Use DL_USE_COLOR to force colorized output. (#1078)
FIX: Updated the unique constraint on the accounts.email column to only be unique when is not deleted. This only fixes PostgreSQL databases; fixing SQLite databases effectively requires rebuilding the entire database, see the comment in the issue for details. (#1109)
FEATURE: Added configuration option for OIDC authentication prompts.
FEATURE: New names>disable_share_token_profanity_check and names>disable_namespace_name_profanity_check configuration options to disable profanity checking for share tokens and namespace names. (#1152)
v2.0.0-rc5
CHANGELOG
This is a pre-release version of zrok v2.0.0. Not all recipes, platforms and distributions have been updated yet.
FEATURE: Major changes to how "unique names" and "reserved sharing" work. See the zrok v2 Migration Guide for details. Reserved sharing, including the zrok reserve, zrok release and zrok share reserved commands have been removed. Namespaces and reserved names replace these concepts in a much more powerful, flexible way which can accomplish what reserved sharing did in a much better way. (#726)
CHANGE: Binary renamed from zrok to zrok2. This allows zrok v1 and v2 to coexist on the same system without conflicts. All command invocations now use zrok2 (e.g., zrok2 enable, zrok2 share public). (#1124)
CHANGE: Environment directory changed from ~/.zrok to ~/.zrok2. This provides complete isolation between v1 and v2 environments. Users running zrok2 enable will create a new environment in ~/.zrok2; existing ~/.zrok environments are not affected. (#1124)
CHANGE: Environment variables renamed from ZROK_* to ZROK2_*. All environment variables now use the ZROK2_ prefix (e.g., ZROK2_API_ENDPOINT, ZROK2_ADMIN_TOKEN, ZROK2_ENABLE_TOKEN). This ensures v1 and v2 environment configurations do not interfere with each other. (#1124)
CHANGE: Linux packages renamed to zrok2, zrok2-agent. The agent's systemd user service file is renamed to zrok2-agent.service. Configuration directory changed to /etc/zrok2. (#1124)
CHANGE: Removed env_v0_3 compatibility layer. Since zrok2 uses ~/.zrok2 exclusively and will never touch ~/.zrok, the v0.3 environment migration code has been removed. The update infrastructure remains for future version upgrades.
FEATURE: zrok2 share private now includes a --share-token flag, which allows a user to create a vanity token for private shares. Now that reserved sharing has been replaced with namespaces, the --share-token flag allows private sharing to retain custom, persistent share token names. (#1070)
FEATURE: zrok2 modify name command available to "upgrade" an ephemeral share name to a reserved share name. If you share something ephemerally and later decide that you want to persist that name for future use you can just zrok2 modify name -r that name and retain it indefinitely (or conversely zrok2 modify name -r=false to schedule a reserved name to be released when an associated share is terminated). (#1066)
FEATURE: New zrok2 list names, zrok2 list namespaces, zrok2 list environments, zrok2 list shares, and zrok2 list accesses commands available to query the environments, shares, and accesses contained in the user's account; supports filtering on activity, accesses, shares, descriptions, host, ip address, and other relevant search criteria. By default outputs human-readable tabular output, but has a --json option to emit the values as JSON. (#1107)
FEATURE: New zrok2 delete environment command that allows for deleting environments other than the current enabled environment. Use zrok2 list environments --idle to find idle environments and remove them using zrok2 delete environment. (#1107)
FEATURE: New zrok2 access dynamicProxy which is designed to work with the new namespaces/names functionality. Rather than parsing the Host header and trying to extract a share token, the new dynamicProxy receives mapping updates from the zrok controller, allowing it to support any kind of mapped name. See the zrok dynamicProxy Guide for details on setting up the new frontend. zrok2 access public remains available for legacy-style setups. (#1041)
FEATURE: The zrok Agent now includes significantly improved handling for subordinate processes in error states. Errors encountered during agent reloading and also during active runtime are retried using an exponential falloff approach. Errored accesses or shares are given transient err_XXXX tokens, which can be used to manage (release) these processes. (#1000)
FEATURE: The zrok Agent has been updated for v2 name selections. Now that "reserved shares" have been replaced with reserved names, the zrok Agent will automatically restart any share which contains a name selection with a reserved name. The Agent continues to automatically manage zrok2 access private processes as always.
FEATURE: zrok2 overview now includes a human-readable default output, that formats the details of your zrok account in an easy-to-understand format. The classic JSON output is still available using the --json flag. (#1064)
FEATURE: zrok2 admin migrate now supports a --down <n> flag, which allows for reverse-migration by a specified number of migrations
CHANGE: The root package path was migrated from github.com/openziti/zrok to github.com/openziti/zrok/v2 to accomodate golang v2+ package naming semantics.
CHANGE: zrok2 status now shows EnvZId instead of Ziti Identity in output. (#1107)
CHANGE: defaultFrontend configuration replaced with new defaultNamespace, which provides the logical equivalent of the old name-handling configuration (#1065)
CHANGE: zrok2 admin create frontend, zrok2 admin update frontend now include a new --dynamic flag which allows setting/changing the value of the dynamic property in the frontend. Setting dynamic is required when configuring a dynamicProxy frontend. zrok2 admin list frontends now displays the dynamic value of the frontends in the system. zrok2 admin list frontends includes a new --extra flag to display the additional/v1 properties maintained for frontends. (#1096)
CHANGE: Completely overhauled the core ziti automation logic. The legacy controller/zrokEdgeSdk package has been replaced with a much more streamlined, clearer package controller/automation. This makes comprehending the controller code a lot simpler. (#1054)
CHANGE: Updated github.com/openziti/sdk-golang to v1.2.4.
CHANGE: All logging migrated from githhub.com/michaelquigley/pfxlog and github.com/sirupsen/logrus to github.com/michaelquigley/df/dl and log/slog. Use environment variable DL_USE_JSON=true to force JSON output. Use DL_USE_COLOR to force colorized output. (#1078)
FIX: Updated the unique constraint on the accounts.email column to only be unique when is not deleted. This only fixes PostgreSQL databases; fixing SQLite databases effectively requires rebuilding the entire database, see the comment in the issue for details. (#1109)
v1.1.11
CHANGELOG
CHANGE: The vpn backend mode has been removed from zrok due to dependency management issues. The underlying TUN device libraries created conflicts that prevented updates to critical dependencies. See the VPN removal guide for migration alternatives and future plans.
CHANGE: Updated github.com/greenpau/caddy-security to v1.1.31. Updated github.com/smallstep/certificates to v0.29.0 (CVE-2025-66406 was reported, but only effects indirect dependencies and not relevant to any viable caddy-security use cases) (#1120)
FIX: the zrok-share.bash wrapper script for Docker and Linux services was updated to use the new spelling of the --oauth-email-address-pattern option (it was --oauth-email-domains until v0.4.26 when it changed to --oauth-email-address-patterns)
v1.1.10
CHANGELOG
OOPS! v1.1.10 is a re-release of the mis-tagged v1.1.9 release. Apologies!
CHANGE: The publicProxy now supports "striped session cookies" to support larger authentication payloads when working with OIDC providers that use larger tokens/payloads. (#1101)
FIX: Fix for icon/favicon in HTML for the api console. (#1094)
v1.1.8
CHANGELOG
CHANGE: The ContextDialer in agent.Controller.NewClient now utilizes the "two-phase" approach to invoking Dial on the remote agent service. First, it attempts to dial the service with the current service list state. If that fails, it will call RefreshService to update the service list and does a second Dial. If the second Dial fails, then the connection fails. This works around service list staleness issues. (#1090)
CHANGE: github.com/openziti/sdk-golang updated to v1.2.8.
CHANGE: CI pull requests now trigger a native-architecture Windows build.
v1.1.7
CHANGELOG
(v1.1.7 is a re-release of v1.1.6; there was a Windows-specific build issue that is corrected in v1.1.7)
FEATURE: The agent.Agent now can optionally enforce that agent remoting starts successfully when creating a new instance. The agent.Config struct has a new RequireRemoting boolean to control this behavior. (#1085)
CHANGE: Additional diagnostic logging in the zrok Agent; details around sub-process executions, etc. (#1084)
v1.1.5
997f93e
michaelquigley
Michael Quigley