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
Is your feature request related to a problem?
ClientBlueprint(libs/ferriskey-cli-core/src/import/mod.rs:94-116) carriesclient_id,name,client_type,protocol,enabled,public_client,service_account_enabled,direct_access_grants_enabled,redirect_urisandroles.Five settings the console exposes have no place in the import file:
post_logout_redirect_uris— without them, logout failsweb_origins— without them, CORS blocks the call to the token endpointThey are therefore outside any import file: not reproducible, and lost on the next realm.
Desired solution
Extend
ClientBlueprintwith those five fields and apply them inapply.rs. All of them should stay optional so existing files keep importing unchanged.Environment
ferris-ctl 0.2.3, FerrisKey server 0.7.0