pub struct ClientCredentials { /* private fields */ }Expand description
Client credentials token issuing process
This state machine will go through four phases. On creation, the request will be validated and
parameters for the first step will be extracted from it. It will pose some requests in the form
of Output which should be satisfied with the next Input data. This will eventually
produce a BearerToken or an Error. Note that the executing environment will need to use
a Registrar, an optional Extension and an Issuer to which some requests should be forwarded.
Issuer ../primitives/issuer/trait.Issuer.html
Registrar ../primitives/registrar/trait.Registrar.html
Extension trait.Extension.html
A rough sketch of the operational phases:
- Ensure the request is valid based on the basic requirements (includes required parameters)
- Try to produce a new token 2.1. Authenticate the client 2.2. Construct a grant based on the request 2.3. Check the intrinsic validity (scope)
- Query the backend for a new (bearer) token
Implementations§
Auto Trait Implementations§
impl Freeze for ClientCredentials
impl RefUnwindSafe for ClientCredentials
impl Send for ClientCredentials
impl Sync for ClientCredentials
impl Unpin for ClientCredentials
impl UnwindSafe for ClientCredentials
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more