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

Support splitting JSON-WS API into multiple ScopeFinders and allow programmatic registration


    • Type: Task
    • Status: In Review
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: Master
    • Fix Version/s: None
    • Component/s: None
    • Labels:


      OAuth2 is a resource oriented authorization protocol. The portal does not have a general concept of resources, but we do support JAX-RS which does. Consequently our OAuth2 provider primarily integrates with this API. However we also support JSON-WS as a single "resource", with scopes contributed by some default SAP entries.

      Though functional, this is creates a confusing end user UX.

      It is expected that the portal admin will only consider these default SAP entries as examples to be replaced by more sensible / specific entries that matches their portal API requirements.

      To help with this, we should allow the JSON-WS "resource" application to be broken down as the portal admin sees fit to complement any available JAX-RS applications.

       This is especially important when needing to provide programmatic installation of a OAuth2 client and related JSON-WS services (for example Liferay Sync). Because then you must isolate these particular JSON-WS services from any scope mapping and prefixing services the portal admin might have applied to the general JSON-WS "resource" application.


          Issue Links



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


                • Created:


                  Version Package