
Questions: 23,676 //
Answers: 52,212 //
Contributing Members: 17,945
i am trying to protect an API with OAuth 2 authentication. I have done the following steps: 1. specified the authentication in RAML. 2. Deployed the API on API Manager. 3. added the policies for "Simple security manager","OAuth 2.0 provider" and OAuth 2.0 access token enforcement.
Now when I am passing the clientID and ClientSecret to make an Oauth2.0 authentication I am getting the following error
"No listener for endpoint: /authorize?scope=&client_id=f567f52336e24f4a8ccd2d4f2a679b53&redirect_uri=http%3A%2F%2Flocalhost%3A8085%2Fconsole%2Fauthentication%2Foauth2.html&response_type=code"
Have I missed Something here?
Are you sure that the HTTP listener is configured to listen at the path /authorize?
Hi , I have configured the endpoint in "OAuth 2.0 provider" policy. Do i have to configure it somewhere else also? and How to configure it ?
You will need to configure a HTTP listener in order to validate the token. Check OAuth example. Let me know if you need further help.
Jul 19, 2017 at 04:32 PM, nahuel answered with:
Hi Harshit! You seem to be using a deprecated oAuth policy that only works on API Gateways prior to v2.0.0. Please, consider using Mule's External oAuth token enforcement, which is the recommended way of enforcing oAuth 2.0 with Mule oAuth provider solution.
The original policy that you are making reference does not work well with listeners but connectors.
Best regards, Nahuel.
Jul 21, 2017 at 09:25 AM, nandabalakrishnan answered with:
Hi, In addition to the above answers, i have doubt regarding your oauth configuration and implementation. you have used your own OAuth provider. you need to configure the /validate resources in the Oauth enforcement policy