Ruman, excellent! Great example. I'm assuming you are training MuleSoft now at Bank of America or somewhere else? I talked too much to be a good teacher, I'm just consulting now. Teaching wasn't for me.
Why am i not seeing OAuth 2.0 Access Token Enforcement Using External Provider policy in the list but OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider
Hi I applied OAUTH2 policy using github as you did by i am facing an error while testing with my endpoint url it throwing an error like client_id is missing but the client is valid i dont the the exact problem can u help us in resolving it. Thank you.
Hi i didnot configured Client ID Enforcement policy , i only applied OAUTH2 access token enforcement policy like you did but im facing an error like client_id missing when i'm testing my url using Postman after getting access token key .
Are you able to access the github resource with the token you generated? If you dont have any other policies, the only place client id is given is when you generate the token. The client id and client secret while generating the token should match the one in your github app.
Unfortunately, the new version of API Manager does not allow this anymore. You can use either one of the recommended OAuth providers or create a custome Mule OAuth provider. Please refer to : docs.mulesoft.com/api-manager/v/2.x/external-oauth-2.0-token-validation-policy Below text taken from the above URL Important: To use the OAuth 2.0 Access Token Enforcement Using External Provider policy, you need a Mule OAuth 2.0 provider to provide an access token. You cannot use any other OAuth 2.0 provider, such as Facebook, Google, or Azure.
Thanks for doing this. I have the same error as the other person mentioned. I directly tried to access a github resource using the access token and it seems to work fine. I do not understand what and where the client_id is missing and what is it complaining about. I do know that this issue is because of the configuration value in the API manager OAuth2 policy. Something about it is not right.
Check the "Skip Client Id Validation" checkbox when you apply the "OAuth 2.0 access token enforcement using external provider policy". It will work after a few seconds.
Very nice and greatly explained & demoed.
Great explanation... Thanks for the video :)
excellent sir..
Ruman, excellent! Great example. I'm assuming you are training MuleSoft now at Bank of America or somewhere else? I talked too much to be a good teacher, I'm just consulting now. Teaching wasn't for me.
Thanks keep uploading more videos
Why am i not seeing OAuth 2.0 Access Token Enforcement Using External Provider policy in the list but OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider
Hi I applied OAUTH2 policy using github as you did by i am facing an error while testing with my endpoint url it throwing an error like client_id is missing but the client is valid i dont the the exact problem can u help us in resolving it.
Thank you.
It sounds like you have client enforcement policy. Can you check if you have any other policies which are applied to the api in api manager?
Hi i didnot configured Client ID Enforcement policy , i only applied OAUTH2 access token enforcement policy like you did but im facing an error like client_id missing when i'm testing my url using Postman after getting access token key .
Are you able to access the github resource with the token you generated? If you dont have any other policies, the only place client id is given is when you generate the token. The client id and client secret while generating the token should match the one in your github app.
The problem is the "Skip Client ID Verification" checkbox while creating the oauth2.0 policy. If unchecked, the above error message pops up.
@Rajasekhar Yenumula you got it worked ??
Thanks you so much , It helping a lot , btw feedback : your voice little low
Unfortunately, the new version of API Manager does not allow this anymore. You can use either one of the recommended OAuth providers or create a custome Mule OAuth provider. Please refer to : docs.mulesoft.com/api-manager/v/2.x/external-oauth-2.0-token-validation-policy
Below text taken from the above URL
Important: To use the OAuth 2.0 Access Token Enforcement Using External Provider policy, you need a Mule OAuth 2.0 provider to provide an access token. You cannot use any other OAuth 2.0 provider, such as Facebook, Google, or Azure.
Thanks for doing this. I have the same error as the other person mentioned. I directly tried to access a github resource using the access token and it seems to work fine. I do not understand what and where the client_id is missing and what is it complaining about. I do know that this issue is because of the configuration value in the API manager OAuth2 policy. Something about it is not right.
Check the "Skip Client Id Validation" checkbox when you apply the "OAuth 2.0 access token enforcement using external provider policy". It will work after a few seconds.
@@robertmax7739 you are right. it worked fine after doing this. thanks for your help!!