Skip to content

API permissions Best Practice #246

Open
@ben-shory

Description

@ben-shory

In the examples the context that is used in the policy contains the HTTP method and URL split.
I expected to see something around the resource, action and maybe some other parameters so the policy is reusable between different modules regardless of the specific invocation method.
Is this just a technical example? Is this considered a best practice? If not, are there resources about P&P?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions