Client-timestamp not updated after secret regeneration on 3scale admin portal

Solution Verified - Updated -

Issue

  • The update-timestamp (attribute updated_at on the 3scale API) of an application is not updated when regenerating a client secret in 3scale GUI.

Environment

  • Red Hat 3scale API Management Platform 2.0 (On-premises), SaaS

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.