Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6296

Redundant feature in usage rules when using app_id & app_key mode

XMLWordPrintable

    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Undefined
    • Workaround Exists
    • Hide

      The workaround is part of the workaround provided for THREESCALE-6295.

      Show
      The workaround is part of the workaround provided for THREESCALE-6295 .

      Current behaviour

      • Service with app_id & app_key mode
      • Under Service > Applications - Settings > Usage Rules there are the following features:
        a) Developers can manage Keys
        b) Allow developers to regenerate access keys

      When using the 2 features, the behaviour is the following:

      • Developers can manage keys => disabled
      • Allow developers to regenerate access keys => enabled/disabled
      • The developers can’t see the app_keys in the dev portal
      • Developers can manage keys => enabled
      • Allow developers to regenerate access keys => enabled
      • The developers can create other app_keys or delete them
      • Developers can manage keys => enabled
      • Allow developers to regenerate access keys => enabled
      • The developers can create other app_keys or delete them

      Summary: the option Allow developers to regenerate access keys is redundant.

       

      Expected behaviour

      • Under Usage Rules it should appear only Developers can manage keys option. 

              Unassigned Unassigned
              rhn-support-avilatus Anna Vila Tusell
              Dominik Hlavac Duran Dominik Hlavac Duran
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: