This article provides information to resolve the error:
Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app
This appears in logs and prevents the cluster from performing scaling actions.
Understand that there are two types of secrets in Azure Kubernetes Service (AKS):
-
Client secret ID
-
Client secret value
The error occurs when the client secret ID is used instead of the client secret value.
-
If the existing client secret value is expired or expiring, generate a new client secret value. When creating the secret value, note that it is visible only once, so make sure to save it securely during creation.
-
Update the configuration with the client secret value (not the client secret ID) using the following API documentation:
After updating the configuration with the correct client secret value, the error will no longer appear, and scaling actions should function as expected.
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago