Skip to content

Releases: dexidp/dex

v2.29.0

29 Jun 15:05
v2.29.0
0780edb
Compare
Choose a tag to compare

The official container image for this release can be pulled from

ghcr.io/dexidp/dex:v2.29.0

Features:

Bugfixes:

Security:

  • Use constant time comparison for client secret verification (#1861, @xtremerui)

Minor changes:

  • Dependency upgrades
  • Tons of small fixes and changes

Find more details in the v2.29.0 milestone.

Many thanks to everyone who contributed to this release!

v2.28.1

20 Mar 20:04
v2.28.1
a1adf86
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

ghcr.io/dexidp/dex:v2.28.1

Bugfixes:

v2.28.0

12 Mar 22:26
v2.28.0
83ad7bc
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

ghcr.io/dexidp/dex:v2.28.0

Features:

  • Add c_hash to id_token, issued on /auth endpoint, when in hybrid flow (#1773, @HEllRZA)
  • Allow configuration of returned auth proxy header (#1839, @seuf)
  • Allow to disable os.ExpandEnv for storage + connector configs by env variable DEX_EXPAND_ENV = false (#1902, @heidemn-faro)
  • Added the possibility to activate lowercase for UPN-Strings (#1888, @VF-mbrauer)
  • Add "Cache-control: no-store" and "Pragma: no-cache" headers to token responses (#1948, @nabokihms)
  • Add gomplate to the docker image (#1893, @nabokihms)
  • Graceful shutdown (#1963, @nabokihms)
  • Allow public clients created with API to have no client_secret (#1871, @spohner)

Bugfixes:

  • Fix the etcd PKCE AuthCode deserialization (#1908, @bnu0)
  • Fix garbage collection logging of device codes and device request (#1918, @nabokihms)
  • Discovery endpoint contains updated claims and auth methods (#1951, @nabokihms)
  • Return invalid_grant error if auth code is invalid or expired (#1952, @nabokihms)
  • Return an error to auth requests with the "request" parameter (#1956, @nabokihms)

Minor changes:

  • Change default themes to light/dark (#1858, @nabokihms)
  • Various developer experience improvements
  • Dependency upgrades
  • Tons of small fixes and changes

v2.27.0

14 Dec 08:58
v2.27.0
0f9e288
Compare
Choose a tag to compare

Action Required

This security release addresses the following advisory: GHSA-m9hp-7r99-94h5

Dex users should immediately update to v2.27.0.

Assets

The official container images for this release can be pulled from:

  • dexidp/dex:v2.27.0
  • ghcr.io/dexidp/dex:v2.27.0

Make sure to always use an image with a version tag.

Changelog since v2.26.0

  • connector/saml: Validate XML roundtrip data before processing request

  • Build the sqlite storage backend via build tag so Dex can compile when cgo is disabled

  • Update image versions

    • golang:1.15.6-alpine3.12
    • postgres:10.15
    • gcr.io/etcd-development/etcd:v3.4.9
  • Copy module dependencies to Docker image for CVE scanning / dependency analysis

Maintenance

  • MAINTAINERS: @srenatus is now Emeritus

  • README.md: Use maintainers list for reporting security issues

  • .github: Add release notes block to pull request template

  • Fully automate dev setup with Gitpod

    Implements a fully-automated development setup using Gitpod.io, an
    online IDE for GitHub and GitLab that enables Dev-Environments-As-Code.
    This makes it easy for anyone to get a ready-to-code workspace for any branch,
    issue or pull request almost instantly with a single click.

  • Enable CodeQL for the Dex repository

  • docs: Fixup broken links

Dependencies

Added

  • github.com/mattermost/xml-roundtrip-validator: 1a8688a
  • gopkg.in/yaml.v3: 9f266ea

Changed

Removed

Nothing has changed.

v2.26.0

05 Nov 15:43
71bbbee
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

dexidp/dex:v2.26.0
ghcr.io/dexidp/dex:v2.26.0

⚠️ As of this release the latest Docker image tag will always point to master. ⚠️
Make sure to always use an image with a version tag.

Features:

Bugfixes:

Minor changes:

v2.25.0

11 Sep 07:07
e837475
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

dexidp/dex:v2.25.0

Features:

Bugfixes:

  • Add offline_access scope in microsoft connector, if required (#1441, @jimmythedog)
  • Allow the google connector to work without a service account (#1720, @candlerb)

Minor changes:

V2 API release

23 Jul 10:48
a8cedc8
Compare
Choose a tag to compare

This release publishes the existing V2 API under a separate module.

The existing API package will remain available for backward compatibility reasons,
but new features will only be added to the new module.

Usage

Although Dex remains backward compatible and continues to provide the API under the original location,
we highly recommend replacing it with the new location in your project (if you use the official API package):

go get github.com/dexidp/dex/api/v2@v2.0.0

Then replace every occurrence of github.com/dexidp/dex/api with github.com/dexidp/dex/api/v2 in your code.

Finally, make sure to get rid of the main Dex module dependency:

go mod tidy

We also recommend using the new API module instead of manually downloading the proto and generating client stubs using protoc.
Read more about the reasons below. (tl;dr: certain future changes might break backward compatibility for these consumers)

History

Dex V2 came with a major rewrite of its API using gRPC and Protobuf.
Consumers of this new API generally followed one of two paths in their applications:

Many users imported the github.com/dexidp/dex/api package directly.
While this worked quite well for most of the time,
it introduced a dependency between consuming projects and the main Dex module itself (with all of its own dependencies).
Sometimes this caused conflicts with other dependencies of the project (aka. dependency hell).
Using Dex this way also forced us to remain backward compatible in a bunch of other areas.

To solve the dependency problem, many consumers decided to download the single proto file from the repository
and generate client stubs themselves. This turned out to be a great alternative to importing the whole Dex project
(just to use its generated API package).

Changes in Protocol Buffers

For quite some time, we wanted to break this status quo.
We tried to steer users away from importing Dex and recommended generating stubs instead.

Ultimately, the recent changes introduced in the Protobuf V2 API for Go lead us to our current solution.
Namely, the new requirement of having a go_package directive in every proto file basically forces us to provide a package with generated code and
makes code generation on the consumer side nearly impossible. (Obviously, someone can hack around this limitation, but it can't be solved nicely)

Although this requirement does not affect us at the moment, since we still use the V1 API for Protobuf,
in the future we might want to upgrade to the new API. So we decided to find a better, official place for the Dex API that consumers can use
without depending on the Dex project itself.

Dedicated API package

We spent some time with experimenting, trying to find the best possible option.
We wanted to find a solution that's backward compatible, but also fits into our future plans with Dex.

After a few iterations, we ended up creating a new package under the original API package, called /v2 and we made it a separate Go module.
This allows us to keep the API close to the main project and lets consumers import the API without the rest of Dex's dependencies.

The first tag of this package is v2.0.0 and we intend to keep versioning this package, separately from the main Dex project.
When adding new features to the API, we will tag new minor versions. Breaking changes will result in a new major version of the API,
which may also result in a major Dex version, but that's still in the future.

Thanks to protobuf's backward compatibility (and our BC promise for the API),
you should be able to talk to Dex with older API versions (compared to the one compiled into Dex itself),
but we recommend using the same version. Although the proto itself should be backward compatible,
the API package depends on gRPC, which is (unfortunately) known to break things between different versions
(thanks to the relatively large shared library).

Future of Dex's API

We have plans to extend the API with new features. Most of them should be backward compatible changes,
so they will likely be added to the v2 API.

That being said, there are a bunch of changes that will break backward compatibility and as such, will require a v3 release.
Although we know it will happen, we don't have it on our near term roadmap. Whether the v2 and v3 will coexist or not is still undecided,
but there is a chance they can.


If you have any questions related to this release, feel free to open an issue or reach out on the #dexidp
channel in the Kubernetes Slack workspace.

v2.24.0

13 May 12:00
v2.24.0
709d416
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

quay.io/dexidp/dex:v2.24.0

Features:

  • Keystone connector: Added Email to Identity (#1681, @kenperkins, @chrigl)
  • Atlassian Crowd connector: allow preferred_username claim to be set (#1684, @ mvdkleijn)
  • Github connector: pass redirect_uri (#1700, @sockmister)
  • server: allow having no secret for static public clients (#1701, @tkleczek)
  • SAML connector: add flag for filtering groups (#1704, @srenatus)

Bug fixes, misc changes:

v2.23.0

18 Mar 09:25
d820fd4
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

quay.io/dexidp/dex:v2.23.0

Features:

Bugfixes:

  • Provider icons use the connector name, not the ID (#1576, @nabokihms)
  • storage/mysql: increase auth_request.state length to 4096 (#1659, @bonifaido )

Minor changes:

v2.22.0

30 Jan 16:27
v2.22.0
26061f9
Compare
Choose a tag to compare

The official docker release for this release can be pulled from

quay.io/dexidp/dex:v2.22.0

Features:

Bugfixes:

Minor changes: