Protecting applications with the use of developers metadata

Instructions on how to protect an application using details on a developer who created the application


Developer metadata can be used for validating policies. It enables, for example, blocking the scope assignment to an application created by a developer identified with specific metadata.


  • You can log in to ACP as an administrator.
  • You have at least one application in ACP.

Select workspace

  1. Navigate to the ACP portal in your browser and log in with your credentials.

  2. In the ACP home page, go to CHANGE WORKSPACE in the sidebar and click to preview available options.

  3. From the CHANGE WORKSPACE menu, select a workspace that you want to configure.

  1. In the workspace, select Applications from the sidebar.

  2. In the Applications view, select an application that you want to check the metadata on.

  3. In the application view, select the Metadata tab.

Identify dev metadata

In the Metadata view, navigate to Developer metadata and review available content, if any.


You’ve learned details on a developer who created the application and you are able to use this data for your purposes.

Create policy

  1. Select Policies from the sidebar.

  2. In the Policies view, select CREATE POLICY.

  3. In the Create Policy view, select the policy type from the drop-down list by setting it to User or Machine to machine.


    Only User and Machine to machine policy types support the developer-metadata validator.

  4. Still in the Create Policy view

    1. Enter Policy name.
    2. Enter Display name.
    3. Set Policy language to CLOUDENTITY.
    4. Select CREATE to proceed.

  5. In the policy generating engine, select ADD VALIDATOR.

  6. From the fly-out Add new validator pane, select Developer.

  7. In the Developer validator, select ADD FIELD.

  8. In the Cross context condition editor, select an attribute for the developer context from the drop-down list, for example URL of the webpage.


    You can also define your own attribute by selecting Custom value from the top of the list of predefined attributes.

  9. Continue the validator setup in the Cross context condition editor:

    1. Select an attribute operator, for example, equals.
    2. Enter a value (target) for your attribute that would validate the policy, for example,
    3. Select SAVE to complete the field setup.
  10. Select the OK icon from the top right corner if you’re done with adding fields.

  11. If you’re done with adding validators, select SAVE to complete the policy setup.


Your policy validating developer metadata is ready to be used.

Next steps

Use the developer metadata for various authorization operations on the 3rd party application in ACP. See, for example, Protecting scopes with access policies as a reference.