From 0a4ed08312ec43618d1c19d2bafb3cf15adc83f6 Mon Sep 17 00:00:00 2001 From: "Michael G. Khmelnitsky" Date: Thu, 2 Nov 2023 23:51:24 -0700 Subject: [PATCH] More validation fixes. --- _includes/content-reuse/qumulo-care-ways-to-get-help.md | 8 ++++++-- .../configuring-saml-single-sign-on-sso.md | 8 ++++++-- .../external-services/using-access-tokens.md | 9 ++++++--- .../watching-file-attribute-directory-changes/rest.md | 2 +- 4 files changed, 19 insertions(+), 8 deletions(-) diff --git a/_includes/content-reuse/qumulo-care-ways-to-get-help.md b/_includes/content-reuse/qumulo-care-ways-to-get-help.md index 3520f268..38580fca 100644 --- a/_includes/content-reuse/qumulo-care-ways-to-get-help.md +++ b/_includes/content-reuse/qumulo-care-ways-to-get-help.md @@ -2,11 +2,15 @@ The Qumulo Care team is always here to help you. You can contact us by using any * 📚 Browse the [Qumulo Knowledge Base](https://care.qumulo.com/hc/en-us/categories/115000637447) -* 🧑‍💻 Open a case by [filing a request](https://care.qumulo.com/hc/en-us/requests/new) or [emailing us](mailto:care@qumulo.com). +* + + 🧑‍💻 Open a case by [filing a request](https://care.qumulo.com/hc/en-us/requests/new) or [emailing us](mailto:care@qumulo.com). * 💬 [Message us on Slack](https://qumulocare.slack.com/) (if you are a current customer). For more information, see our [Slack Tips and Tricks](https://docs.qumulo.com/contacting-qumulo-care-team.html#slack-tips-and-tricks). -* 📱 Call one of our toll-free numbers: +* + + 📱 Call one of our toll-free numbers: * **North America:** [+1 855-577-7544](tel:+18555777544) diff --git a/administrator-guide/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md b/administrator-guide/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md index a43a601c..44e109ba 100644 --- a/administrator-guide/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md +++ b/administrator-guide/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md @@ -20,9 +20,13 @@ Before you begin, make sure that you have done the following. * To allow the cluster to find group memberships for SAML-authenticated users, configure the Base DN in your AD configuration, even if you don't use POSIX attributes. -* Ensure that your SAML Identity Provider (IdP) is linked to the same AD. An _identity provider_ (such as Azure AD, Duo, or Okta) is a system that authenticates users (for example, by using passwords and additional factors). +* - Typically, an IT department manages an IdP centrally and the IdP is linked with AD. Before you can enable SSO, your IT department must register a new Service Provider (SP) in your IdP. A _service provider_ is the server which users access, in this case a Qumulo cluster. + Ensure that your SAML Identity Provider (IdP) is linked to the same AD. An _identity provider_ (such as Azure AD, Duo, or Okta) is a system that authenticates users (for example, by using passwords and additional factors). + + + + Typically, an IT department manages an IdP centrally and the IdP is linked with AD. Before you can enable SSO, your IT department must register a new Service Provider (SP) in your IdP. A _service provider_ is the server which users access, in this case a Qumulo cluster. {% include note.html content="You can use trusts, as long as the Base DN covers all users that might require access to your cluster." %} diff --git a/administrator-guide/external-services/using-access-tokens.md b/administrator-guide/external-services/using-access-tokens.md index feffcfc4..bd65fa18 100644 --- a/administrator-guide/external-services/using-access-tokens.md +++ b/administrator-guide/external-services/using-access-tokens.md @@ -47,7 +47,9 @@ Use the `auth_create_access_token` command and specify the user. For example: $ qq auth_create_access_token jane ``` -You can: + + +You can: * Specify the user as a name * Qualify the user by using a domain prefix, for example: * `ad:jane` @@ -64,7 +66,9 @@ $ qq auth_create_access_token jane {{site.data.alerts.end}} -The `auth_create_access_token` command returns a JSON response that contains the bearer token body and the access token ID, which you can use to manage the access token. + + +The `auth_create_access_token` command returns a JSON response that contains the bearer token body and the access token ID, which you can use to manage the access token. ```json { @@ -140,7 +144,6 @@ To use the credentials file, specify its location by using the `--credentials-st $ qq --credentials-store ./qumulo_credentials who_am_i ``` - ## Getting Metadata for Access Tokens {{page.varPrereqRead}} This section explains how to get metadata for a specific access token or all access tokens by using the `qq` CLI. diff --git a/administrator-guide/watching-file-attribute-directory-changes/rest.md b/administrator-guide/watching-file-attribute-directory-changes/rest.md index 174bbd39..3f75d55d 100644 --- a/administrator-guide/watching-file-attribute-directory-changes/rest.md +++ b/administrator-guide/watching-file-attribute-directory-changes/rest.md @@ -70,7 +70,7 @@ The following is a list of available notification types in [SSE event payloads]( - +
Notification TypeNotification Type Description