GITBOOK-3715: No subject

HealthSamurai · Dec 4, 2024 · 784e634 · 784e634
1 parent 211eef2
commit 784e634
Show file tree

Hide file tree

Showing 15 changed files with 45 additions and 41 deletions.
diff --git a/SUMMARY.md b/SUMMARY.md
@@ -317,18 +317,18 @@
     * [Authentication Tutorial](modules/security-and-access-control/readme-1-1/basic-auth-tutorial.md)
     * [Creating user & set up full user access](modules/security-and-access-control/readme-1-1/creating-user-and-set-up-full-user-access.md)
     * [Restricting Access to Patient Data](modules/security-and-access-control/readme-1-1/restricting-access-to-patient-data.md)
+    * [Create and test access control](modules/security-and-access-control/readme-1-1/access-policy.md)
+    * [RBAC](modules/security-and-access-control/readme-1-1/rbac/README.md)
+      * [Flexible RBAC built-in to Aidbox](modules/security-and-access-control/readme-1-1/rbac/role-based-access-policies.md)
+      * [RBAC with JWT containing role](modules/security-and-access-control/readme-1-1/rbac/role-based-access-control-with-jwt-containing-role.md)
+      * [RBAC with ACL](modules/security-and-access-control/readme-1-1/rbac/role-based-access-control-with-acl.md)
+    * [Set-up token introspection](modules/security-and-access-control/readme-1-1/token-introspection.md)
+    * [Prohibit user to login](modules/security-and-access-control/readme-1-1/configuration-options.md)
+    * [Debug access control](modules/security-and-access-control/readme-1-1/debug.md)
   * [How-to guides](modules/security-and-access-control/how-to-guides/README.md)
-    * [Create and test access control](modules/security-and-access-control/how-to-guides/access-policy.md)
-    * [RBAC](modules/security-and-access-control/how-to-guides/rbac/README.md)
-      * [Flexible RBAC built-in to Aidbox](modules/security-and-access-control/how-to-guides/rbac/role-based-access-policies.md)
-      * [RBAC with JWT containing role](modules/security-and-access-control/how-to-guides/rbac/role-based-access-control-with-jwt-containing-role.md)
-      * [RBAC with ACL](modules/security-and-access-control/how-to-guides/rbac/role-based-access-control-with-acl.md)
     * [SMART on FHIR](modules/security-and-access-control/how-to-guides/smart-on-fhir/README.md)
       * [Set up SMART on FHIR in Aidbox](modules/security-and-access-control/how-to-guides/smart-on-fhir/smart-on-fhir-app-launch.md)
       * [Get a SMART App launched](modules/security-and-access-control/how-to-guides/smart-on-fhir/smart-of-fhir.md)
-    * [Set-up token introspection](modules/security-and-access-control/how-to-guides/token-introspection.md)
-    * [Prohibit user to login](modules/security-and-access-control/how-to-guides/configuration-options.md)
-    * [Debug access control](modules/security-and-access-control/how-to-guides/debug.md)
   * [Technical reference](modules/security-and-access-control/readme-1/README.md)
     * [User, Session, Client resources](modules/security-and-access-control/readme-1/overview.md)
     * [Tokens processing](modules/security-and-access-control/readme-1/tokens-processing.md)

diff --git a/getting-started/versioning-and-release-notes/release-notes.md b/getting-started/versioning-and-release-notes/release-notes.md
diff --git a/modules/security-and-access-control/how-to-guides/smart-on-fhir/README.md b/modules/security-and-access-control/how-to-guides/smart-on-fhir/README.md
@@ -1,2 +1,6 @@
+---
+hidden: true
+---
+
 # SMART on FHIR
 
diff --git a/...ss-control/how-to-guides/access-policy.md → ...ccess-control/readme-1-1/access-policy.md b/...ss-control/how-to-guides/access-policy.md → ...ccess-control/readme-1-1/access-policy.md
diff --git a/...ol/how-to-guides/configuration-options.md → ...ntrol/readme-1-1/configuration-options.md b/...ol/how-to-guides/configuration-options.md → ...ntrol/readme-1-1/configuration-options.md
diff --git a/...and-access-control/how-to-guides/debug.md → ...ty-and-access-control/readme-1-1/debug.md b/...and-access-control/how-to-guides/debug.md → ...ty-and-access-control/readme-1-1/debug.md
diff --git a/...cess-control/how-to-guides/rbac/README.md → ...-access-control/readme-1-1/rbac/README.md b/...cess-control/how-to-guides/rbac/README.md → ...-access-control/readme-1-1/rbac/README.md
diff --git a/...bac/role-based-access-control-with-acl.md → ...bac/role-based-access-control-with-acl.md b/...bac/role-based-access-control-with-acl.md → ...bac/role-based-access-control-with-acl.md
diff --git a/...ccess-control-with-jwt-containing-role.md → ...ccess-control-with-jwt-containing-role.md b/...ccess-control-with-jwt-containing-role.md → ...ccess-control-with-jwt-containing-role.md
diff --git a/...guides/rbac/role-based-access-policies.md → ...me-1-1/rbac/role-based-access-policies.md b/...guides/rbac/role-based-access-policies.md → ...me-1-1/rbac/role-based-access-policies.md
diff --git a/...ty-and-access-control/readme-1-1/relationship-based-access-control-in-aidbox.md b/...ty-and-access-control/readme-1-1/relationship-based-access-control-in-aidbox.md
@@ -25,7 +25,7 @@ Our security policy says:
 
 > _User has access to all studies they collaborate on and to all patient records within those studies._
 
-Authorization model that best suits our task is [relationship-based access control](https://en.wikipedia.org/wiki/Relationship-based\_access\_control) (ReBAC). It states that _'subject's permission to access a resource is defined by the presence of relationships between those subjects and resources'_.
+Authorization model that best suits our task is [relationship-based access control](https://en.wikipedia.org/wiki/Relationship-based_access_control) (ReBAC). It states that _'subject's permission to access a resource is defined by the presence of relationships between those subjects and resources'_.
 
 We will focus only on read access, expecting that all data is uploaded. We will upload prepared sample data later on implementation section.
 
@@ -489,7 +489,7 @@ And we met this requirement using ReBAC authorization model. In order to achieve
 
 ### What's next
 
-Writing access policies may be tricky some time, Aidbox has tooling to [debug AccessPolicy](../how-to-guides/debug.md).
+Writing access policies may be tricky some time, Aidbox has tooling to [debug AccessPolicy](debug.md).
 
 ## Talk to a Health Samurai Engineer
 

diff --git a/modules/security-and-access-control/readme-1-1/restrict-resource-operations.md b/modules/security-and-access-control/readme-1-1/restrict-resource-operations.md
@@ -104,4 +104,4 @@ Aidbox router stores data in the request object:
 
 Access policy engine evaluates request object. And here it checks that `operation.id` property contains either `Read` or `FhirRead` string.
 
-You can inspect request object [using `__debug` query parameter](../how-to-guides/debug.md#\_\_debug-query-string-parameter).
+You can inspect request object [using `__debug` query parameter](debug.md#__debug-query-string-parameter).
diff --git a/...trol/how-to-guides/token-introspection.md → ...control/readme-1-1/token-introspection.md b/...trol/how-to-guides/token-introspection.md → ...control/readme-1-1/token-introspection.md
diff --git a/modules/security-and-access-control/security/simple-role-based-access-control.md b/modules/security-and-access-control/security/simple-role-based-access-control.md
@@ -12,8 +12,8 @@ Each `Role` resource assigns a role to a `User.` `AccessPolicy` resource has an
 
 ## Guide: flexible RBAC
 
-{% content-ref url="../how-to-guides/rbac/role-based-access-policies.md" %}
-[role-based-access-policies.md](../how-to-guides/rbac/role-based-access-policies.md)
+{% content-ref url="../readme-1-1/rbac/role-based-access-policies.md" %}
+[role-based-access-policies.md](../readme-1-1/rbac/role-based-access-policies.md)
 {% endcontent-ref %}
 
 ## Create a patient
@@ -100,4 +100,4 @@ Aidbox router stores data in the request object:
 
 Access policy engine evaluates request object. And here it checks that `user.roles[].value` property contains `practitioner` string.
 
-You can inspect request object [using `__debug` query parameter](../how-to-guides/debug.md#\_\_debug-query-string-parameter).
+You can inspect request object [using `__debug` query parameter](../readme-1-1/debug.md#__debug-query-string-parameter).
diff --git a/...s/security-and-access-control/smart-on-fhir/smart-scopes-for-limiting-access.md b/...s/security-and-access-control/smart-on-fhir/smart-scopes-for-limiting-access.md
@@ -27,7 +27,7 @@ To enable scope checking in the Access Control layer, the JWT access token must
 
 &#x20;\* - required claim
 
-For scope checking, Aidbox accepts any valid JWT tokens issued by [external servers](../how-to-guides/token-introspection.md) if they contain the specified scopes and Aidbox can issue its own JWT tokens with all the required claims.
+For scope checking, Aidbox accepts any valid JWT tokens issued by [external servers](../readme-1-1/token-introspection.md) if they contain the specified scopes and Aidbox can issue its own JWT tokens with all the required claims.
 
 ### Example&#x20;
Original file line number	Diff line number	Diff line change
Expand Up		@@ -104,4 +104,4 @@ Aidbox router stores data in the request object:

		Access policy engine evaluates request object. And here it checks that `operation.id` property contains either `Read` or `FhirRead` string.

		You can inspect request object [using `__debug` query parameter](../how-to-guides/debug.md#\_\_debug-query-string-parameter).
		You can inspect request object [using `__debug` query parameter](debug.md#__debug-query-string-parameter).