Skip to content

Support for connector managed token validity #4923

Description

@chancez

Preflight Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

I'm interested in building a RADIUS connector for Dex and one thing that RADIUS supports is sending clients a Session-Timeout attribute, which indicates how long the authentication session should be valid for. In Dex, the expiration for tokens is dictated by the configuration, and connectors cannot influence expiration based on the currently defined interfaces.

Proposed Solution

Two ideas:

  • Add an optional Expiration or MaxAge to the connector.Identity field that, if set, Dex uses to set the expiration for tokens issued using this connector.
  • Add a new optional interface for connectors that can given a connector.Identity returns how long a session is valid for. Connectors could encode the expiration into the ConnectorData field, and the method could extract expiration from the ConnectorData to return the Expiration/MaxAge of the session.

Alternatives Considered

No response

Additional Information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions