Adding missing URL / (#2591)

* Adding missing URL / * Fix archived or deleted links * jwt.io is now 500
cloud-gov · Jan 29, 2025 · 08726fe · 08726fe
1 parent 7a88796
commit 08726fe
Show file tree

Hide file tree

Showing 7 changed files with 8 additions and 6 deletions.
diff --git a/.lycheeignore b/.lycheeignore
@@ -55,6 +55,8 @@ https://public.cyber.mil/dccs/
 https://dl.dod.cyber.mil/wp-content/uploads/cloud/zip/U_Cloud_Computing_SRG_V1R4.zip
 https://www.microsoft.com/en-us/security/mobile-authenticator-app
 https://csrc.nist.gov/projects/risk-management/fisma-background
+# JWT.IO works in the browser, but fails in curl or from link checker (thanks, CloudFlare/Heroku)
+https://jwt.io
 
 # example urls in docs
 https://cfpyapi.app.cloud.gov/get_table
diff --git a/_docs/compliance/domain-standards.md b/_docs/compliance/domain-standards.md
@@ -74,7 +74,7 @@ requirement.
 
 cloud.gov does not currently support DNSSEC on `cloud.gov` domains. For example, an application at `*.app.cloud.gov` would not support DNSSEC.
 
-[OMB memo M-18-23](https://www.whitehouse.gov/wp-content/uploads/2018/08/M-18-23.pdf) rescinds M-08-23, the OMB memo that originally mandated DNSSEC for federal systems. You should consider carefully whether DNSSEC is still a requirement for your system.
+[OMB memo M-18-23](https://bidenwhitehouse.archives.gov/wp-content/uploads/2018/08/M-18-23.pdf) rescinds M-08-23, the OMB memo that originally mandated DNSSEC for federal systems. You should consider carefully whether DNSSEC is still a requirement for your system.
 
 If you do need DNSSEC for your custom domain, you are responsible for configuring DNSSEC in your DNS system. cloud.gov can't configure DNSSEC for you because cloud.gov does not have access to your DNS system.
 

diff --git a/_docs/compliance/logging-requirements.md b/_docs/compliance/logging-requirements.md
@@ -5,7 +5,7 @@ sidenav: true
 title: M-21-31 compliance
 ---
 
-This document outlines how our platform enables cloud.gov customers to comply with logging requirements specified by [OMB Memorandum M-21-31](https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf). If you have any questions about this document, please contact [[email protected]](mailto:[email protected]).
+This document outlines how our platform enables cloud.gov customers to comply with logging requirements specified by [OMB Memorandum M-21-31](https://bidenwhitehouse.archives.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf). If you have any questions about this document, please contact [[email protected]](mailto:[email protected]).
 
 ## EL1 Compliance
 

diff --git a/_docs/compliance/meeting-tic-requirements.md b/_docs/compliance/meeting-tic-requirements.md
@@ -11,7 +11,7 @@ Agencies hosting workloads on cloud.gov need to ensure compliance
 with the [DHS CISA Trusted Internet
 Connections](https://www.cisa.gov/tic-guidance)
 program.  In September 2019, OMB released [Memo
-M-19-26](https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf),
+M-19-26](https://bidenwhitehouse.archives.gov/wp-content/uploads/2019/09/M-19-26.pdf),
 that specified new standards for TIC 3.0, and DHS CISA is currently
 developing new guidance for workloads hosted in PaaS cloud environments.
 

diff --git a/_kbarticles/2024-12-06-migrating-opensearch.md b/_kbarticles/2024-12-06-migrating-opensearch.md
@@ -109,7 +109,7 @@ The screenshot below show some of the major changes to the user interfaces, such
 
 The Cloud.gov team has implemented OpenSearch to deliver a number of benefits to our customers. Among these are:
 
-* Twelve months of live access to system logs, in alignment with [M-21-31](https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf).
+* Twelve months of live access to system logs, in alignment with [M-21-31](https://bidenwhitehouse.archives.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf).
 * Definitions of saved searches and visualizations are now isolated by OpenSearch tenants that correspond to Cloud.gov organizations.
   * You no longer need to worry about choosing a globally unique name.
   * If you share the same saved object across multiple orgs, you will need to import it into each of your orgs.

diff --git a/_posts/2017-02-02-fedramp-authorized.md b/_posts/2017-02-02-fedramp-authorized.md
@@ -7,7 +7,7 @@ redirect_from:
 ---
 
 ### Now it’s easier than ever to get started with cloud.gov.
-We’re delighted to announce that cloud.gov has received a FedRAMP Joint Authorization Board (JAB) Provisional Authority to Operate (P-ATO) at the Moderate impact level. This means that cloud.gov successfully completed a comprehensive security and compliance assessment performed by a board of the CIOs and their teams from the General Services Administration, the Department of Defense, and the Department of Homeland Security. cloud.gov is the [first completely open source service to receive FedRAMP authorization](https://www.gsa.gov/blog/2017/02/02/cloudgov-becomes-first-fully-open-source-fedramp-solution). Teams can now use cloud.gov with less upfront work, so they can use cloud.gov to deliver services even faster.
+We’re delighted to announce that cloud.gov has received a FedRAMP Joint Authorization Board (JAB) Provisional Authority to Operate (P-ATO) at the Moderate impact level. This means that cloud.gov successfully completed a comprehensive security and compliance assessment performed by a board of the CIOs and their teams from the General Services Administration, the Department of Defense, and the Department of Homeland Security. cloud.gov is the first completely open source service to receive FedRAMP authorization. Teams can now use cloud.gov with less upfront work, so they can use cloud.gov to deliver services even faster.
 
 [Read more about how this new authorization can help your team.](https://18f.gsa.gov/2017/02/02/cloud-gov-is-now-fedramp-authorized/)
 <!--more-->

diff --git a/_posts/2025-01-02-v2api-deprecation.md b/_posts/2025-01-02-v2api-deprecation.md
@@ -34,7 +34,7 @@ versions, if applicable:
   `🚨 [WARNING] Outdated CF CLI version - please upgrade: https://github.com/cloudfoundry/cli/releases/latest 🚨`
   * You **may** continue using unsupported clients until v2 is discontinued.
   * If you need to reinstall/upgrade your client, follow our [documentation]({{site.baseurl}}/docs/getting-started/setup/#set-up-the-command-line)
-* `cf-cli` plugins. Our Cloud.gov documentation references a [number of useful plugins]({{site.baseurl}}docs/management/plugins/), their current [v3 Plugin Status](#plugin-status) is detailed in the table below.
+* `cf-cli` plugins. Our Cloud.gov documentation references a [number of useful plugins]({{site.baseurl}}/docs/management/plugins/), their current [v3 Plugin Status](#plugin-status) is detailed in the table below.
   * For "pending" plugins, periodically check the linked GitHub issues for status.
   * For plugins with no update pending, seek an alternative.
 * CF API client libraries such as [cf-java-client](https://github.com/cloudfoundry/cf-java-client), [go-cfclient](https://github.com/cloudfoundry/go-cfclient), or [cf-python-client](https://github.com/cloudfoundry-community/cf-python-client/issues/220):