Managing Scopes
    • 07 Mar 2024
    • 3 Minutes to read
    • Dark
      Light
    • PDF

    Managing Scopes

    • Dark
      Light
    • PDF

    Article summary

    This documentation focuses on the complete lifecycle of Scopes in the Authorization Platform, from creation to modification, and deletion.
    Follow the relevant sections to navigate through Scope management. Check out About Scopes to learn more.

    Backwards Compatibility
    As of PlainID's January 2024 release (5.2402), Scope Management allows users to set two new properties affecting how Authorization Requests are authenticated and how the PDP evaluates Identities. Existing Scopes operate in backward compatibility mode, with no change in behavior. The new properties are not defined by default to maintain backward compatibility, and existing Scopes are marked as incomplete. Users are advised to update the latest Policy Authorization Agent (PAA) and configure Scopes by selecting an Identity Matching Type and a Scope Auth Method based on their use-case. Once saved, the Scope will function according to the new settings. Also in this release, JWKs URL Settings for JWT validation are managed in the Scopes section within Environment Settings. Users are recommended to transfer JWKs Settings from the PAA to the new JWT Settings side-panel in the Scopes and Identity Templates sections after updating PAA and Scope definitions. Note that the JWKs Settings option in the PAA will soon be deprecated. For details on Identity Matchers and Scope Authentication, refer to Managing Identity Matchers and Managing Scope Authentication.

    Permissions
    • Tenant Admins & Environment Admins: Can update and change Scope settings.
    • Environment Viewers: Can view the Scope setup in View Mode only.

    Creating a New Scope

    Scopes can be created on the Environment Settings screen and then modified or deleted.

    To create a new Scope:

    1. From the Environment Settings screen, select Scopes. The List of Scopes screen is displayed.

    2. Click Create Scope. The New Scope screen is displayed.

    3. Enter the Name of the new Scope.

    4. Click Select Applications and select one or more Applications.

    5. Define the Cache Duration (Min). Within the Scope, the Authorization Platform manages the authorization credentials as well as the runtime response cache duration. The Cache Duration Minimum indicates the amount of time the Authorization Response is cached. The maximum value for this is 1440 minutes (24 hours). The default value is 0 minutes. For more information, see Caching Options

    6. Select an Identity Matcher Type. You can set up the mapping for in the Managing Identity Matchers section. For more information, refer to Identity Requests from a Virtual Source or navigate to the Identity Workspace Documentation and see the Managing Identity Matchers article.

    7. Select an Authentication Method. You can learn more about Scope Authentication and validating the JWT Settings in the Managing Scope Authentication article.

    8. Click Create. The new Scope is added to the list of Scopes.

    Modifying a Scope

    To modify a Scope:

    1. From the Environment Settings screen, select Scopes. The List of Scopes screen is displayed.
    2. Select the Scope you want to modify.
    3. Adjust the input fields according to your modifications. You can update the Application, Identity Matcher Type, Authentication Method, and JWT Validation.
    4. Save your changes by clicking Continue on the bottom of the screen.

    See Managing Identity Matchers and Managing Scope Authentication for more information on Identity Matchers and Scope Authentication.

    Deleting a Scope

    To delete a Scope:

    1. Hover over the Scope you wish to delete. Two buttons are displayed: Manage Keys and Delete Scope.
    2. Click Delete Scope. A confirmation message is displayed.
    3. Click Delete. The Scope is deleted.

    Identity Requests from a Virtual Source

    Users have the ability to shape their authorization processes at the Scope level through a dual-method approach within the dynamic confines of the Identity Workspace Settings. This offers users greater control, reduces dependencies on external data sources, and enhances customization options.

    Identity Matchers and Requests

    Users can set up an Identity Matching Type by specifying one of two methods in the Scope and managing it in the Identity Workspace Settings. They can send information in a request or by utilizing Identity Matchers. Each option plays a distinct role in the Authorization process while offering flexibility and control over how Identity information is handled, while ensuring a more granular validation process.

    • Send in Request
      In a Request flow, send the Identity ID and Type as mandatory fields in the Authorization request. If they are not sent, the flow will use a default Identity Template (A single Identity Workspace template or the default ‘User’ template). If there is no match to the Identity Template or the Identity ID is missing, users will receive an error message.

    • Use Identity Matchers
      In a Matcher flow, you can utilize Identity Template Matchers and Identity ID Mappers to decide which Identity Template and ID are used in the Authorization request. This process should be used in cases where a JWT is sent as part of the request and is meant to identify the Identity. Check out the Identity Workspace Settings to learn how to use Matchers.


    Was this article helpful?