X-Git-Url: https://git.squeep.com/?a=blobdiff_plain;f=docs%2Fdevelopment%2Fauthentication_authorization.md;h=f9a1a763fbed739de3486f11570ecb7d0b6750c9;hb=becf7dced6c051326f33dd201ac25d38af341b24;hp=183bfc2c94facbaff8584274bd03c12e1f6ac440;hpb=6284e8f4b2e9b737d1ed256e89f2ac3ba673d6f8;p=akkoma diff --git a/docs/development/authentication_authorization.md b/docs/development/authentication_authorization.md index 183bfc2c9..f9a1a763f 100644 --- a/docs/development/authentication_authorization.md +++ b/docs/development/authentication_authorization.md @@ -2,7 +2,7 @@ ## OAuth token-based authentication & authorization -* Pleroma supports hierarchical OAuth scopes, just like Mastodon but with added granularity of admin scopes. For a reference, see [Mastodon OAuth scopes](https://docs.joinmastodon.org/api/oauth-scopes/). +* Akkoma supports hierarchical OAuth scopes, just like Mastodon but with added granularity of admin scopes. For a reference, see [Mastodon OAuth scopes](https://docs.joinmastodon.org/api/oauth-scopes/). * It is important to either define OAuth scope restrictions or explicitly mark OAuth scope check as skipped, for every controller action. To define scopes, call `plug(Pleroma.Web.Plugs.OAuthScopesPlug, %{scopes: [...]})`. To explicitly set OAuth scopes check skipped, call `plug(:skip_plug, Pleroma.Web.Plugs.OAuthScopesPlug )`.