Apigee integrated portal shows keys as "active" even if not approved for an API product

Google Cloud Apigee
,
1

Greetings-

My organization is an Apigee X cloud user. We also use Apigee’s “integrated portal” for publishing our API catalog and for developers to register their apps, get keys, etc.

In the Apigee integrated portal (developer portal), when a developer creates an app and subscribes to an API product, the default status of the key is “active” even if the API product the person has subscribed to requires manual approval and that approval has not happened yet.

And, in a scenario where the developer has created two or more keys for their app, and they have subscribed to two or more API products, there is no way for them to tell in the developer portal which key has been approved for which product.

It feels like we are experiencing a disconnect between how developer credentials are stored and displayed in the Apigee console in GCP vs how they are displayed in the integrated portal. In the Apigee console, when you open up the “app details” view under distribution/apps, there is a separate tile displayed for each credential (key/secret pair) and on each of those tiles it lists the API products and the approval status of each (pending or approved). In the developer portal, there is no equivalent hierarchy of credential->product->approval status. If the developer portal was more akin to the way the information is organized in the Apigee console, then consumers would be more clear on the status of each key / API product combination and whether or not their key(s) have been approved yet.

Does anyone know if there is a setting we can use in the developer portal to create better alignment between how this information appears in the Apigee console and the developer portal? Perhaps there is something we’re missing. Alternatively, if it can’t be fixed with configuration on our part, is there a standard procedure we can follow to determine if this is in the product roadmap for the integrated developer portal? And if not, how can we put that request in so it can be considered by the product managers?

Thanks for any guidance.

2 Likes
2

Thank you for your question, @PeterHBristol ! We’re following this thread and making sure it gets the attention it deserves. We’re also inviting the community to join in and share their expertise.

3

Thank you for the report. We agree this is not ideal behavior, and expect to address this in a forthcoming release. We’ll update this post when the fix is released.

1 Like
4

An update - we are currently working on a fix to make this experience clearer. We don’t expect to offer to the consumer developer a full list of products and the approval status of each, but we would like to more accurately represent the approval status of the key (all approved, some approved, not approved). The admin will continue to be able to see the full list of products and approval status, and will be needed regardless in order to modify any approval status.

5

that sounds like a step in the right direction! thanks, Peter

6

This is fix released now. https://cloud.google.com/apigee/docs/api-platform/publish/portal/release-notes

Thanks -Sean

1 Like