Skip to content

External connectors #1907

@nabokihms

Description

@nabokihms

Is your feature request related to a problem?

The main problem that the Dex repo contains a lot of different connectors with various features, purposes, original authors, tests coverage, etc.

It makes Dex maintainers support a lot of custom logic that they are unfamiliar with.

Describe the solution you'd like to see

The thing to start with is writing solid design documentation (an enhancement proposal, you may say).

Nowadays, the most popular solution to this kind of problem is to develop a GRPC API interface. Connectors will be distributed as programs that implement this interface (with the separate codebase, tests, maintainers, etc.)

Examples: terraform providers, Kubernetes CSI.

Describe alternatives you've considered

If we want to move Dex forward, there are not so many good alternatives. It is possible to limit the number of connectors in the core repo and stop merging PR with new connectors until stabilizing already accepted ones. However, this looks like something other than a prospective way.

Additional context

The initial idea and its benefits were previously described in a slack thread.

Proposed solutions

List of previously proposed connectors

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions