diff --git a/docs/docs/users/guides/methods_filtering.md b/docs/docs/users/guides/methods_filtering.md index ab7d4d11020c..f81802ef3535 100644 --- a/docs/docs/users/guides/methods_filtering.md +++ b/docs/docs/users/guides/methods_filtering.md @@ -10,7 +10,7 @@ sidebar_position: 4 When running a Filecoin node, you might want to restrict the RPC methods that are available to the clients. This can be useful for security reasons, to limit the exposure of the node to the internet, or to reduce the load on the node by disabling unnecessary methods. :::note -[JWT authentication](../knowledge_base/jwt_handling) is a different way to restrict access to the node. It allows you to authorize certain operations on the node using JWTs. However, JWT restrictions are hard-coded in the node and cannot be changed dynamically. If you want to make sure that a certain read-only method is not available to the clients, you can use the method filtering feature. +[JWT authentication](../reference/json-rpc/authentication) is a different way to restrict access to the node. It allows you to authorize certain operations on the node using JWTs. However, JWT restrictions are hard-coded in the node and cannot be changed dynamically. If you want to make sure that a certain read-only method is not available to the clients, you can use the method filtering feature. The methods are first filtered by the method filtering feature, and then the JWT authentication is applied. If a method is disallowed by the method filtering, the JWT token will not be checked for this method. ::: diff --git a/docs/docs/users/knowledge_base/jwt_handling.md b/docs/docs/users/reference/json-rpc/authentication.md similarity index 99% rename from docs/docs/users/knowledge_base/jwt_handling.md rename to docs/docs/users/reference/json-rpc/authentication.md index 3c1faab45ebb..468867fe5b2b 100644 --- a/docs/docs/users/knowledge_base/jwt_handling.md +++ b/docs/docs/users/reference/json-rpc/authentication.md @@ -1,5 +1,6 @@ --- -title: JWT Authentication +title: Authentication +sidebar_position: 1 --- # JWT Authentication :key: diff --git a/docs/docs/users/reference/json-rpc/overview.md b/docs/docs/users/reference/json-rpc/overview.md index d9afc5a4ad0e..b6baa0a6c139 100644 --- a/docs/docs/users/reference/json-rpc/overview.md +++ b/docs/docs/users/reference/json-rpc/overview.md @@ -43,6 +43,6 @@ Access control is implemented for certain methods. Levels of access include: - Write - Admin -Authentication is performed via [JWT Tokens](../../knowledge_base/jwt_handling). When starting Forest use `--save-token ` to store an `Admin` token, +Authentication is performed via [JWT Tokens](./authentication). When starting Forest use `--save-token ` to store an `Admin` token, otherwise the token will be printed in the logs during startup. With this token you can call the methods `AuthNew` to generate additional tokens as needed.