Struct RegistrationConfig 

#[non_exhaustive]
pub struct RegistrationConfig {
    pub registration_endpoint: Option<String>,
    pub allowed_grant_types: Vec<GrantType>,
    pub allowed_scopes: ScopeSet,
    pub client_secret_ttl: Option<Duration>,
    pub management_enabled: bool,
}

What dynamic registration is allowed to produce here. Held behind crate::server::ServerConfig::registration, which is None (registration off) by default.

Every bound below is a CEILING on what an anonymous, or merely policy-approved, registrant can obtain. The defaults are the narrow ones on purpose; see RegistrationConfig::new. #[non_exhaustive]: this struct’s field set VARIES WITH CARGO FEATURES, so a host that writes a full struct literal has a build that breaks the day anything in their dependency graph enables a feature they did not ask for. Construct with new() and assign the fields you want. This is the one attribute on this type that cannot be added after publication, because by then somebody’s struct literal is in production.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

registration_endpoint: Option<String>

RFC 8414 section 2 registration_endpoint. None derives {issuer}/register.

allowed_grant_types: Vec<GrantType>

The grants a registration may ask for. Anything outside this list is invalid_client_metadata.

allowed_scopes: ScopeSet

The ceiling on a registration’s scope. A request outside it is invalid_client_metadata; the default is EMPTY, so a host must say what a registrant may reach.

client_secret_ttl: Option<Duration>

How long an issued client secret lives. None (the default) means it never expires, which is what client_secret_expires_at: 0 says on the wire (RFC 7591 section 3.2.1).

management_enabled: bool

Whether RFC 7592 read, update and delete are offered at all. true by default: a client that can be created and never corrected or deleted leaves the host doing registration lifecycle by hand.

Implementations

impl RegistrationConfig

pub fn new() -> Self

The narrow defaults: the authorization code grant with refresh, no scopes, management on.

client_credentials and the device grant are deliberately absent. A client_credentials registration mints tokens with NO resource owner anywhere in the picture, so an open registration endpoint that grants it is an open token endpoint; the device grant makes the registrant able to allocate user codes, which RFC 8628 section 5.1 says are only adequate in combination with rate limiting. Both are one line for a host to add, with its eyes open.

pub fn endpoint(&self, issuer: &str) -> String

The advertised registration endpoint for issuer.

Trait Implementations

impl Clone for RegistrationConfig

fn clone(&self) -> RegistrationConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RegistrationConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for RegistrationConfig

fn default() -> Self

Returns the “default value” for a type.

impl Eq for RegistrationConfig

impl PartialEq for RegistrationConfig

fn eq(&self, other: &RegistrationConfig) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for RegistrationConfig