[SCIM 3/4]: SCIM client token CRUD + Bearer auth #9180
+1,736
−340
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,99 @@ | ||
| // This Source Code Form is subject to the terms of the Mozilla Public | ||
| // License, v. 2.0. If a copy of the MPL was not distributed with this | ||
| // file, You can obtain one at https://mozilla.org/MPL/2.0/. | ||
|
|
||
| //! SCIM-only bearer tokens | ||
| use super::super::Details; | ||
| use super::HttpAuthnScheme; | ||
| use super::Reason; | ||
| use super::SchemeResult; | ||
| use crate::authn; | ||
| use async_trait::async_trait; | ||
| use headers::HeaderMapExt; | ||
| use headers::authorization::{Authorization, Bearer}; | ||
|
|
||
| // This scheme is intended only for SCIM provisioning clients. | ||
| // | ||
| // For ease of integration into existing clients, we use RFC 6750 bearer tokens. | ||
| // This mechanism in turn uses HTTP's "Authorization" header. In practice, it | ||
| // looks like this: | ||
| // | ||
| // Authorization: Bearer oxide-scim-01c90c58085fed6a230d137b9b9b5e7501d0a523 | ||
| // ^^^^^^^^^^^^^ ^^^^^^ ^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| // | | | | | ||
| // | | | +--- specifies the token itself | ||
| // | | +--------------- specifies this "token" mechanism | ||
| // | +---------------------- specifies RFC 6750 bearer tokens | ||
| // +------------------------------------- standard HTTP authentication hdr | ||
| // | ||
| // (That's not a typo -- the "authorization" header is generally used to specify | ||
| // _authentication_ information. Similarly, the "Unauthorized" HTTP response | ||
| // code usually describes an _authentication_ error.) | ||
|
|
||
| pub const SCIM_TOKEN_SCHEME_NAME: authn::SchemeName = | ||
| authn::SchemeName("scim_token"); | ||
|
|
||
| /// Prefix used on the bearer token to identify this scheme | ||
| // RFC 6750 expects bearer tokens to be opaque base64-encoded data. In our case, | ||
| // the data we want to represent (this prefix, plus valid tokens) are subsets of | ||
| // the base64 character set, so we do not bother encoding them. | ||
| const TOKEN_PREFIX: &str = "oxide-scim-"; | ||
|
|
||
| /// Implements a SCIM provisioning client specific bearer-token-based | ||
| /// authentication scheme. | ||
| #[derive(Debug)] | ||
| pub struct HttpAuthnScimToken; | ||
|
|
||
| #[async_trait] | ||
| impl<T> HttpAuthnScheme<T> for HttpAuthnScimToken | ||
| where | ||
| T: ScimTokenContext + Send + Sync + 'static, | ||
| { | ||
| fn name(&self) -> authn::SchemeName { | ||
| SCIM_TOKEN_SCHEME_NAME | ||
| } | ||
|
|
||
| async fn authn( | ||
| &self, | ||
| ctx: &T, | ||
| _log: &slog::Logger, | ||
| request: &dropshot::RequestInfo, | ||
| ) -> SchemeResult { | ||
| let headers = request.headers(); | ||
| match parse_token(headers.typed_get().as_ref()) { | ||
| Err(error) => SchemeResult::Failed(error), | ||
| Ok(None) => SchemeResult::NotRequested, | ||
| Ok(Some(token)) => match ctx.scim_token_actor(token).await { | ||
| Err(error) => SchemeResult::Failed(error), | ||
| Ok(actor) => SchemeResult::Authenticated(Details { actor }), | ||
| }, | ||
| } | ||
| } | ||
| } | ||
|
|
||
| fn parse_token( | ||
| raw_value: Option<&Authorization<Bearer>>, | ||
| ) -> Result<Option<String>, Reason> { | ||
| let token = match raw_value { | ||
| None => return Ok(None), | ||
| Some(bearer) => bearer.token(), | ||
| }; | ||
|
|
||
| if !token.starts_with(TOKEN_PREFIX) { | ||
| // This is some other kind of bearer token. Maybe another scheme knows | ||
| // how to deal with it. | ||
| return Ok(None); | ||
| } | ||
|
|
||
| Ok(Some(token[TOKEN_PREFIX.len()..].to_string())) | ||
| } | ||
|
|
||
| /// A context that can look up a Actor::Scim from a token. | ||
| #[async_trait] | ||
| pub trait ScimTokenContext { | ||
| async fn scim_token_actor( | ||
| &self, | ||
| token: String, | ||
| ) -> Result<authn::Actor, Reason>; | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good to say that by "non-user actor" you mean the SCIM arm of the match. It's obvious when you're looking at the diff but might not be so obvious later.