Uploaded image for project: 'PUBLIC - OAuth2'
  1. PUBLIC - OAuth2
  2. OAUTH2-160

No scope mapper configuration behaves differently to having one named "Default" with Metatype defaults stored

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: Master, 1.0-portal_7.1.0
    • Fix Version/s: 1.0-portal_7.1.0
    • Component/s: None
    • Labels:
      None

      Description

      The scope mapper configuration metatype provides mappings for HTTP verb named scopes ("GET", "PUT" etc) because these mean nothing to end users. It sensibly groups + maps them to "everything", "everything.read" and "everything.write".

      However at present with no stored configuration these mappings are not in place.

      Additionally it feels odd that if you go to create a new configuration and simply save it without changing the defaults provided by the metatype, then the system behaves differently.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package
                1.0-portal_7.1.0