Skip to content

Authorization server selection is first-in-list for pre-provisioned providers #3844

Open

Description

@LHMisme420

With no issuer configured, _select_authorization_server returns advertised[0], and _preferred_authorization_server only filters by issuer when one is set, falling back to advertised[0] otherwise. So the resource server's list order decides which authorization server receives the pre-provisioned provider's Basic auth, which carries a durable client_secret rather than an expiring bearer.

Is first-in-list the intended selection when the list carries more than one server, and how would you classify a durable client secret placed with the first entry of a list the resource server controls?

Activity

  1. media-ctrl commented on Nov 9, 2026

    @media-ctrl
  2. LHMisme420 commented on Nov 9, 2026

    @LHMisme420
    Author

    Thanks for confirming it's construction rather than accident. Two readings then, and I want to get them right.

    Passing issuer is the fix and it's available now, since _require_metadata_for_configured_issuer already drops non-matching metadata. So the exposure is any deployment that hasn't set it, which is the default.

    Fail-closed on a multi-entry list with no issuer is the part not in the tree. Worth knowing whether that's a 3.0 plan or still open, because until it ships, the safe default is a config choice the operator has to know to make, and the deprecation warning is the only thing telling them

  3. media-ctrl commented on Nov 9, 2026

    @media-ctrl
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

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions