Skip to content

docs: clarify that .read and .manage scopes are independent #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mjdavidson wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify that .read and .manage scopes are independent #69

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -697,8 +697,8 @@ Then restart your MCP client so the server picks up the new scope list.
> [!TIP]
> Start with the minimum set of scopes your use-case requires. For example, if you only need to read users and brands, use `okta.users.read okta.brands.read`. Adding `okta.*.manage` scopes enables write operations — only grant those if needed.

> [!NOTE]
> Scopes follow the pattern `okta.<resource>.read` for read-only access and `okta.<resource>.manage` for full read+write access. You do **not** need both — `okta.users.manage` implicitly enables all read operations on users.
> [!IMPORTANT]
> `.read` and `.manage` are independent — **`.manage` does not imply `.read`**. Each tool requires exactly one scope (see the table above): read and list tools need `okta.<resource>.read`, write tools need `okta.<resource>.manage`. If you grant only `okta.apps.manage`, the write tools load but `list_applications` and `get_application` stay disabled because they require `okta.apps.read`. To get both read and write tools for a resource, include **both** scopes, e.g. `okta.apps.read okta.apps.manage`.

## �🔐 Authentication

Expand Down
3 changes: 2 additions & 1 deletion src/okta_mcp_server/utils/scope_registry.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,8 @@
Scope naming convention:
``okta.<resource>.read`` — GET operations (read-only).
``okta.<resource>.manage`` — POST / PUT / DELETE operations (write).
A token with ``*.manage`` implicitly covers ``*.read`` for the same resource.
These are independent: a token with ``*.manage`` does NOT grant ``*.read``.
To use both read and write tools for a resource, configure BOTH scopes.

Reference: https://developer.okta.com/docs/api/oauth2
"""
Expand Down