Repository navigation
Dex CLI v1.7.0
Breaking Changes
None.
Changes
- Dex Web accepts connector manifests whose OAuth endpoints and scopes come from connection settings.
authorizationEndpoint,tokenEndpoint,scopes,credentialDerivations[].endpoint,tokenEndpointAuthMethodandtokenRequestEncodingmay each be a literal or{"fromSetting": "<setting>"}.- OAuth start resolves references from the connection's settings, with field defaults applied, and rejects a missing or invalid setting with HTTP 400
CONNECTOR_OAUTH_SETTING_INVALIDbefore the browser leaves. The message names the setting and never echoes its value. tokenEndpointAuthMethod: client_secret_basicsends the client credentials with HTTP Basic.- Requests to an endpoint that a setting supplies resolve the host once, check every address and dial only checked addresses. Plain http is allowed only when every address is loopback or private; link-local addresses, including the cloud metadata address, are always refused. Proxies are ignored and redirects are not followed. Release literals stay HTTPS-only.
See #620.
- OAuth start resolves references from the connection's settings, with field defaults applied, and rejects a missing or invalid setting with HTTP 400
- The run Overview in Dex Web can set an Attribute and publish a Channel message on a live run, with JSON, string, int64, double and boolean values. See #615.
dexcli devincludes the SQL Attribute Store changes of Server v1.6.0 and v1.6.1: row key templates, snake_case column naming, AttributeMap child tables, and the schema refresh when a batch writes an unknown column. See #617, #618 and #619.
Full changelog: cli-v1.6.4...cli-v1.7.0