Infrastructure/logto
0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2025-02-17 22:04:19 -05:00
Code Issues Activity

refactor(console): remove redundant notification from m2m guide (#5954)

Browse source
This commit is contained in:
Xiao Yijun 2024-05-31 13:17:40 +08:00 • committed by GitHub
parent b8ea4800c5
commit 9861b8ac44
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 0 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
packages/console/src/assets/docs/guides/m2m-general/README.mdx
View file

@ -14,10 +14,6 @@ Machine-to-machine (M2M) is a common practice to authenticate if you have an app
Since Logto uses RBAC as its access control policy, assigning M2M roles to M2M apps is necessary for protecting your API which needs direct service talk.
<InlineNotification>
To learn our current RBAC and the difference between user role and M2M role, see <a href="https://docs.logto.io/docs/recipes/rbac/manage-permissions-and-roles/">Manage permissions and roles</a> to learn more
</InlineNotification>
There are two common use cases of using machine-to-machine apps in Logto:
1. **Accessing Logto Management API**: In this case, you need to assign a M2M role that include the `all` permission from the built-in Logto Management API to your M2M app.