Details

    • Type: Sub-Task
    • Status: In Progress
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.0-portal_7.1.0
    • Fix Version/s: 1.0-portal_7.1.0
    • Component/s: None
    • Labels:
      None

      Description

      What developer and admin roles do we expect? 

      • 3rd party backend Liferay developer
        • register JAX-RS app into OAuth2
        • expose scopes and localization for them
        • optionally check scopes using their custom impl
        • May distribute via Liferay Marketplace (i.e. no knowledge of deployment environment)
      • 3rd party JAX-RS developer
        • Creates standard JAX-RS applications 
        • No Liferay awareness or build dependencies, just JSR-* dependent
      • Deployment developer / technical portal admin
        • ScopeMapper to rename/re-map scopes, group them
        • Configure ScopeMatcher for hierarchical scopes (ChunkScopeMatcherFactory)- enable, disable (StrictScopeMatcherFactory) or implement own
        • Configure PrefixHandlerFactory to isolate application scopes using BundleNamespacePrefixHandlerFactory or break isolation and group multiple JAX-RS apps together using own impl
      • Non-technical admin
        • Use UI to rename/re-map scopes, group them
        • Should not require understanding of HTTP verb best practice (assist when deploying standard JAX-RS apps)
        • Use UI to assign available PrefixHandlerFactory(s) to JAX-RS apps

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:

                  Packages

                  Version Package
                  1.0-portal_7.1.0