OAuth 2.0 access token enforcement using Mule OAuth provider policy | Mule 4.3.0| API Manager

Поділитися
Вставка
  • Опубліковано 29 сер 2024
  • This video is specifically created for demonstrating the capability of OAuth Provider module available in exchange to create as an Mule Oauth app which can be configured at API Manager for policy implementation.
    Code reference: github.com/anc...

КОМЕНТАРІ • 3

  • @nrtmule4687
    @nrtmule4687 3 роки тому

    Hi Ankur, Looks like Client_Id and Client_secret are hardcoded in the demo. Is there a way we can automate generation of them and how do we impose "Client ID Validation" i.e. APP1 and APP2 are using OAUTH Mulesoft app and 2 clients CL1 and CL2 will have access to only APP1 and APP2 respectively. How can we perform Client ID Validation ?

  • @MrPmmelvin
    @MrPmmelvin 4 роки тому

    Hi Sir , here in this method the token is not expiring. That is if the ttl expiration time is set as 60 sec , even after 60 sec the token will work. Could you please help on this

    • @MuleExpert
      @MuleExpert  4 роки тому

      I would suggest to have a look on code logic. Please navigate to github.com/ancur4u/MuleasOauth2Provider.git. Using the logic, if it is a invalid or expired token it will result in "The token received: WHx8wa5dQfp54HoIcNzZlyO9CoR1AiSsPaIuHy_RdPdiq-Xqwb62tO9su93DPM3sJLXW12AkQgdN9QuWIjlCrg , is not valid".