From fcf784a800341e1a5eb650b24d6b5b78bb3fbc29 Mon Sep 17 00:00:00 2001
From: Coki <hashcookie404@gmail.com>
Date: Sun, 22 Sep 2024 01:00:31 +0800
Subject: [PATCH 1/3] chore: update docs link check config to include
 n-able.com

---
 .github/workflows/docs.links.check.config.json | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.github/workflows/docs.links.check.config.json b/.github/workflows/docs.links.check.config.json
index b5654f26c..386e7c0b4 100644
--- a/.github/workflows/docs.links.check.config.json
+++ b/.github/workflows/docs.links.check.config.json
@@ -38,6 +38,9 @@
         },
         {
             "pattern": "^https://www.bytebase.com/docs"
+        },
+        {
+            "pattern": "^https://www.n-able.com/"
         }
     ]
 }
\ No newline at end of file

From 75b7fb3b1da9c4cadc6629724698bb879f5f0cc4 Mon Sep 17 00:00:00 2001
From: Coki <hashcookie404@gmail.com>
Date: Sun, 22 Sep 2024 01:21:28 +0800
Subject: [PATCH 2/3] docs: update CAS Protocol Specification link to version
 7.1.x

---
 docs/how-to-connect/cas.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/how-to-connect/cas.md b/docs/how-to-connect/cas.md
index 17a48ee63..ebd082ea9 100644
--- a/docs/how-to-connect/cas.md
+++ b/docs/how-to-connect/cas.md
@@ -23,7 +23,7 @@ The CAS endpoint prefix in Casdoor is `<Casdoor endpoint>/cas/<organization name
 - `/p3/proxyValidate` endpoint: `https://door.casdoor.com/cas/casbin/cas-java-app/p3/proxyValidate`
 - `/samlValidate` endpoint: `https://door.casdoor.com/cas/casbin/cas-java-app/samlValidate`
 
-For more information about CAS, its different versions, and parameters for these endpoints, refer to the [CAS Protocol Specification](https://apereo.github.io/cas/6.6.x/protocol/CAS-Protocol-Specification.html).
+For more information about CAS, its different versions, and parameters for these endpoints, refer to the [CAS Protocol Specification](https://apereo.github.io/cas/7.1.x/protocol/CAS-Protocol-Specification.html).
 
 ### An Example
 

From a091ec31fab70be85d3b71e2cdbf32ca2edc6bb4 Mon Sep 17 00:00:00 2001
From: Coki <hashcookie404@gmail.com>
Date: Sun, 22 Sep 2024 01:39:14 +0800
Subject: [PATCH 3/3] docs: update Hasura permission rules documentation link

---
 docs/integration/Haskell/Hasura.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/integration/Haskell/Hasura.md b/docs/integration/Haskell/Hasura.md
index f564d85f1..9dc326b33 100644
--- a/docs/integration/Haskell/Hasura.md
+++ b/docs/integration/Haskell/Hasura.md
@@ -44,7 +44,7 @@ Refer to the image below for reference.
 
 The next step is to create a `user` role for the app. Users should be able to see only their records but not other people's records.
 
-Configure the `user` role as shown in the image below. For more information, read about [configuring permission rules in Hasura](https://hasura.io/docs/latest/graphql/core/auth/authorization/permission-rules/).
+Configure the `user` role as shown in the image below. For more information, read about [configuring permission rules in Hasura](https://hasura.io/docs/2.0/auth/authorization/permissions/).
 
 ![Picture showing how to set permissions in Hasura](https://graphql-engine-cdn.hasura.io/learn-hasura/assets/graphql-hasura-authentication/keycloak/hasura-set-permissions.png)