Skip to content

The import blueprint covers only part of a client #25

Description

@jorisvilardell

Is your feature request related to a problem?

ClientBlueprint (libs/ferriskey-cli-core/src/import/mod.rs:94-116) carries client_id, name, client_type, protocol, enabled, public_client, service_account_enabled, direct_access_grants_enabled, redirect_uris and roles.

Five settings the console exposes have no place in the import file:

  • post_logout_redirect_uris — without them, logout fails
  • web_origins — without them, CORS blocks the call to the token endpoint
  • the PKCE requirement
  • the Device Authorization grant toggle
  • per-client token lifetimes

They are therefore outside any import file: not reproducible, and lost on the next realm.

Desired solution

Extend ClientBlueprint with those five fields and apply them in apply.rs. All of them should stay optional so existing files keep importing unchanged.

Environment

ferris-ctl 0.2.3, FerrisKey server 0.7.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions