From 7d8b95e1a313f88558797ed97df8cc67466a05a4 Mon Sep 17 00:00:00 2001 From: Alexa Kristensen <81787716+akristen@users.noreply.github.com> Date: Thu, 26 Mar 2026 16:03:13 -0500 Subject: [PATCH] GitHub issues updates (#24292) PR to address 4 GitHub issues assigned to my docs areas. --- content/manuals/billing/payment-method.md | 7 +++---- .../enterprise/security/single-sign-on/FAQs/idp-faqs.md | 7 ++++++- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/content/manuals/billing/payment-method.md b/content/manuals/billing/payment-method.md index 94baea9b20..89cab5904f 100644 --- a/content/manuals/billing/payment-method.md +++ b/content/manuals/billing/payment-method.md @@ -237,11 +237,10 @@ verification email and enter the amount of this deposit to verify your account. ## Failed payments -You can't manually retry a failed payment. Docker will retry failed payments -based on the retry schedule. +If your payment fails, select **Pay now**. This redirects you from Docker Hub so you can manually retry the payment through Stripe. -If your subscription payment fails, there is a grace period of 15 days, -including the due date. Docker retries to collect the payment 3 times using the +You have a grace period of 15 days +including the due date when your payment fails. Docker retries to collect the payment 3 times using the following schedule: - 3 days after the due date diff --git a/content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md b/content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md index 66e99b874e..d983696056 100644 --- a/content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md +++ b/content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md @@ -27,7 +27,12 @@ To turn on SSO in Docker, you need the following from your IdP: ## What happens if my existing certificate expires? -If your certificate expires, contact your identity provider to retrieve a new X.509 certificate. Then update the certificate in the [SSO configuration settings](/manuals/enterprise/security/single-sign-on/manage.md#manage-sso-connections) in the Docker Admin Console. +Contact your identity provider to retrieve a new X.509 certificate. Update with the new certificate in [SSO configuration settings](/manuals/enterprise/security/single-sign-on/manage.md#manage-sso-connections) from Docker Admin Console. + +- If your organization enforces SSO, username and password credentials won't work. +- If your organization doesn't enforce SSO, users can sign in with their username and password credentials. + +If you need additional help, contact [Docker support](https://app.docker.com/support/contact). ## What happens if my IdP goes down when SSO is turned on?