CURL to Generate Access Token is not working when disabled "Client Credential" grant type
Describe your problem(s)
Once after disabling the client-credentials grant type, the 'CURL TO GENERATE ACCESS TOKEN' button also not working(after clicking it, there are no any outcome) even the password grant type selected for the particular application.When disabling the client-credentials grant type, it is removing the 'GENERATE ACCESS TOKEN' button and adds the 'Enable Client Credentials grant type to generate test access tokens' message. Which is expected and working fine.

Describe your solution
In a scenario like, password grant enabled and client credentials grant disabled for an application, then I guess it would be good to have the CURL generation button with only the password grant details.
Suggested Labels:
APIM-4.0.0 latest update level of 4.0.0.4
When the password grant is enabled and the client credentials grant is disabled for an application, the CURL generation button is available.
But it includes details for both the password grant and the client credentials grant, even though the client credentials grant is disabled. (in the latest version)
Hi @chamilaadhi I’d like to reserve this issue. I can update the CURL generation logic so that when the client-credentials grant is disabled (but password grant is enabled), the generated CURL only includes password grant details, ensuring correct behavior.
Hi, I’m interested in working on this issue for Hacktoberfest. Could you confirm if it’s still available?
@dhananjayaaps you can work on this issue.
@Iduranga-Uwanpriya Since we have already assigned you a couple of issues, we would like to give others a chance as well. Once you complete the existing issues, we will assign you a new one.
Thank you @chamilaadhi I’ll start working on this and will open a PR as soon as possible.
Hi @dhananjayaaps how is the progress of this issue?
I am still working on this and will try to fix it as soon as possible.
Hey @dhananjayaaps, were you able to open a PR?
Hi @dhananjayaaps, Do you have any update on the progress of this issue?