Hi Sir , Can you please add a video for grant_type = Authorization Code as well , not finding anywhere , please explain the concept in video itself , i mean a detailed video on that as how you usually do 😀 thanks in advance 😀😀
If I publish my api to exchange and generate client credentials there, I want it to get stored in the client_os you showed in the video, can you please explain how this can be achieved. Thanks.
Very much informative video. Is there anyway I can store the token in DB table itself instead of putting in OS because OS is removed when node is down in RTF?
Hi Jitendra Bafna, Thanks for all your mule videos its very helpful . Question on this video from where did you get the client id and secret which you used to create client. Is it random unique id which is now serving as client credentials and stored in object store? And where is the token generated /token api?
Hi there Ruchi as per My understanding, the client credetials are randomly given to store in the object store...and next thing in the global elements while creating and configuring the Oauth 2 provider will be confiured with token object store ....at that time by default listener configuration is created with the /token as its endpoint.....The same component now works for creating the client and generating the token as well....Hope u get it Ruchi Good Day
Hi Jitendra, very good informative video. One question, in real life scenario, is it recommended to have just one OAuth app(createclient, validate flow) deployed and let all CH Mule APIs use one common app for OAuth?
@jitendra Bafna. Excellent video sir. One clarification. So the token validation is happening through policy and we are hitting the okta end point. Okta has rate limiting right.will this validation be performed each time a call s made even though we have the token lifetime?
Bro some emergency doubt i have login api success which have validations of Oauth but after api success to reneder page with details from the frontend there are some api’s calling like device info and basic info those are getting token not valid issue though they dont have any validations in the flow any suggestions?
If the Mule OAuth provider application is hosted on a few load-balanced servers with mule's hybrid approach, how can I ensure that the token gets successfully validated even if the gateway calls the instance that did not create the token? Is Object store shared across the servers on the environment?
@Jitendara - Thanks for the video. I have used you video as reference for setting Mule as Oauth2 provider. I have added the additional setting of Total ttl=120 and Token ttl timeout unit= Seconds. As per my expectation post 120 seconds the /validation endpoint should throw an error as the access_token issued is expired now. But its validating the token successfully and allowing me to access the resources on which I applied this policy. Can you help me how I can make sure my access_token is expired after 120 seconds
Melvin hey ya, I tired setting ttl 120 sec and expiration interval as 30 mins in token object store settings, as I made 30 mins expiration then the token is been removed in 30 mins and I get error message , but still i don’t get a message as token expired after 120 sec which I expect .
@@lavanyamailz1 it's a Bug, working with Mule support team. We have identified a workaround - keep a Choice router at the end of the flow based on Validate Token component response to be specific expires_in field. If its expired raise error otherwise send success response to client.
Can you please reply ?? I just followed this video and My token is not expiring , I set ttl 120 sec and I manage to get success result back . Please reply I have a presentation to show this and I am stuck .,
Melvin did you tried giving token ttl 120 sec in oauth2 provider config ?? So I gave 120 sec in both places and it worked for me .. in oauth settings and in token object store
Hi Jitendra, Nicely explained Just want to knw when applied policy in api manager,do we need to give the correct client id and secret we get which we requested in portal.or it can b random client id? When i am using random client id,token is generated successfully but when hitting my service it is giving error "invalid client"
Hi Jitendra, I have created exactly the same flow however my main service is not returning the error message when the token is not valid but i can see invalid token message in oauth provider service. so is there something that i am missing to declare in main service. your help will be appreciated.
I have a doubt here, sorry i just started learning Mule and running into lot of confusions ,So .. Can someone tell me in the first Url, create client [10:06][ we are passing the client id and client secret , how did we get the values ,?] is that randomly we have given a key , secret and creating client with them or ..?
Did you get how these values are generated? I am assuming that these values are just created manually and used because there is no validation for these client id and secret.
Hi, I'm getting this error org.mule.runtime.core.internal.util.store.MuleObjectStoreManager: Running expiry on partition AuthorizationCodes of org.mule.runtime.core.internal.store.PartitionedPersistentObjectStore@59d3ab9c threw java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0:Index 0 out of bounds for length 0 Have anyone faced the same? If yes, how did you resolve?
