mart-w/kanidm
1
0
Fork 0
mirror of https://github.com/kanidm/kanidm.git synced 2025-02-23 20:47:01 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Resolve codespell issues (#1753)

Browse source
This commit is contained in:
Firstyear 2023-06-20 13:19:21 +10:00 committed by GitHub
parent 8b331325ae
commit 8d2565773e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
6 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
book/src/developers/designs/kanidm-trust.rst
View file

@ -37,7 +37,7 @@ There are different ways we can scope a trust out, each with pros-cons. Here are
is no global catalog, just the details you get in the presented authentication (certificate). You is no global catalog, just the details you get in the presented authentication (certificate). You
may implement some controls around which subject DN's to allow/deny, but this is pretty fraught may implement some controls around which subject DN's to allow/deny, but this is pretty fraught
with landminds. You don't know who exists until they login! with landminds. You don't know who exists until they login!
* Azure AD individiual account trusting. Instead of trusting a whole domain you allow a user from * Azure AD individual account trusting. Instead of trusting a whole domain you allow a user from
a remote tennant to access your resources. You don't trust everyone in their tennant, just that a remote tennant to access your resources. You don't trust everyone in their tennant, just that
one account that you can invite. You can then revoke them as needed. one account that you can invite. You can then revoke them as needed.
* Group-trust - FreeIPA does this with AD. It's still like kerberos, but you only trust a subset * Group-trust - FreeIPA does this with AD. It's still like kerberos, but you only trust a subset

2
book/src/developers/designs/replication.rst
View file

@ -385,7 +385,7 @@ server of the change. A psudeo example of this is:
Summarised, this shows that on our server, our changelog has changes from A for time range Summarised, this shows that on our server, our changelog has changes from A for time range
T4 to T8, B T6 to T16, and C T0 to T7. T4 to T8, B T6 to T16, and C T0 to T7.
Individiually, a RUV does not allow much, but now we can compare RUVs to another server. Lets Individually, a RUV does not allow much, but now we can compare RUVs to another server. Lets
assume a second server exists with the RUV of: assume a second server exists with the RUV of:
:: ::

2
server/lib/src/idm/credupdatesession.rs
View file

@ -375,7 +375,7 @@ impl<'a> IdmServerProxyWriteTransaction<'a> {
if !eperm_search_primary_cred || !eperm_mod_primary_cred || !eperm_rem_primary_cred { if !eperm_search_primary_cred || !eperm_mod_primary_cred || !eperm_rem_primary_cred {
security_info!( security_info!(
"Requestor {} does not have permission to update credentials of {}", "Requester {} does not have permission to update credentials of {}",
ident, ident,
account.spn account.spn
); );

2
server/lib/src/idm/oauth2.rs
View file

@ -2244,7 +2244,7 @@ mod tests {
== Oauth2Error::InvalidClientId == Oauth2Error::InvalidClientId
); );
// * mis match origin in the redirect. // * mismatched origin in the redirect.
let auth_req = AuthorisationRequest { let auth_req = AuthorisationRequest {
response_type: "code".to_string(), response_type: "code".to_string(),
client_id: "test_resource_server".to_string(), client_id: "test_resource_server".to_string(),

4
server/lib/src/idm/scim.rs
View file

@ -278,7 +278,7 @@ impl<'a> IdmServerProxyWriteTransaction<'a> {
if !eperm.delete { if !eperm.delete {
security_info!( security_info!(
"Requestor {} does not have permission to delete sync account {}", "Requester {} does not have permission to delete sync account {}",
sfe.ident, sfe.ident,
sync_account.name sync_account.name
); );
@ -403,7 +403,7 @@ impl<'a> IdmServerProxyWriteTransaction<'a> {
if !eperm.delete { if !eperm.delete {
security_info!( security_info!(
"Requestor {} does not have permission to delete sync account {}", "Requester {} does not have permission to delete sync account {}",
ste.ident, ste.ident,
sync_account.name sync_account.name
); );

2
server/lib/src/server/access/mod.rs
View file

@ -57,7 +57,7 @@ pub enum Access {
#[derive(Debug, Clone, PartialEq, Eq)] #[derive(Debug, Clone, PartialEq, Eq)]
pub struct AccessEffectivePermission { pub struct AccessEffectivePermission {
// I don't think we need this? The ident is implied by the requestor. // I don't think we need this? The ident is implied by the requester.
// ident: Uuid, // ident: Uuid,
pub target: Uuid, pub target: Uuid,
pub delete: bool, pub delete: bool,