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

Lookup account by provider_key or service_token

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Minor
    • SaaS
    • None
    • System

    Description

      From kibana monitoring, we get provider_key or service_token as identifiers of requests.

      Sometimes we need to identify the developer account running those requests. This functionality is available from UI (search account). But this information cannot be fetched using 3scale API which is the gateway used by 3scale CLI.

      One endpoint of the 3scale API doing similar search is

      admin/api/accounts/find.xml

      But this endpoint only works with username, user_id and email.

      The requested lookup based on provider_key or service_token can be implemented extending the mentioned endpoint or exposing new endpoint. Implementation details up to you

      The information required can be the same returned by

      admin/api/accounts/find.xml

      <?xml version="1.0" encoding="UTF-8"?>
      <account>
      <id>some id</id>
      <created_at>2018-10-30T22:56:29+01:00</created_at>
      <updated_at>2018-10-30T22:56:29+01:00</updated_at>
      <state>created</state>
      <org_name>BLA</org_name>
      <extra_fields></extra_fields>
      <monthly_billing_enabled>true</monthly_billing_enabled>
      <monthly_charging_enabled>true</monthly_charging_enabled>
      <credit_card_stored>false</credit_card_stored>
      <plans> ... </plans>
      <users> ... </users>
      </account>

      Attachments

        Activity

          People

            Unassigned Unassigned
            eguzki Eguzki Astiz Lezaun
            Peter Stanko Peter Stanko (Inactive)
            Michal Macejko Michal Macejko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: