Very helpful video to learn oAuth in mule 4. Thanks for explaining in detail.
@muletechnologyacademy-zero56254 жыл бұрын
Thanks
@snehareddy53302 жыл бұрын
Hi Jitendra, thankyou very much for this informative session
@NidhiSharma-sq8oy4 жыл бұрын
great,,, very helpful to understand complete Oauth concept alongwith implementation...
@muletechnologyacademy-zero56254 жыл бұрын
Thanks
@shashikantpatel012 жыл бұрын
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 😀😀
@anu3784 жыл бұрын
Very helpful video sir. Thank you 😊
@nitishchauhan22892 жыл бұрын
Very helpful. Thank you for explaining this topic.
@lokeshtalluri84324 жыл бұрын
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.
@MarioScarfiglieri5 ай бұрын
is there a video to see how u set up the test-app-cloud?
@prudhvibethamchrla72303 жыл бұрын
Can you please update video to cover, implementation for refresh_token scenario as well
@shashikantpatel012 жыл бұрын
Need similar video on grant_type = Authorization Code please
@abhisheksolanki2241 Жыл бұрын
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?
@ravellavenkatsubbaiah4957 Жыл бұрын
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?
@arunmittal77164 жыл бұрын
Very well explained. Thanks
@suryaandey36112 жыл бұрын
Hi Jitendra ,one doubt why claims are not available in Mulesoft provided token is there any way to get it.
@muletechnologyacademy-zero56252 жыл бұрын
I don’t think so.
@suryaandey36112 жыл бұрын
@@muletechnologyacademy-zero5625 ohk I tried multiple ways but luck,, Thanks for information
@AverageFishingGuy4 жыл бұрын
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?
@satishraodarmakkolla53984 жыл бұрын
@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
@lavanyamailz14 жыл бұрын
Same here, the token is not expiring ,, did you manage to fix it ?? Please reply
@lavanyamailz14 жыл бұрын
Did you fix it ?? Please reply , I am stuck with this
@MrPmmelvin4 жыл бұрын
Hi Did you manage to fix the issue.
@lavanyamailz14 жыл бұрын
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 .
@satishraodarmakkolla53984 жыл бұрын
@@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.
@ruchijain56032 жыл бұрын
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?
@balajichowdary61862 жыл бұрын
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
@sekarbabu87333 жыл бұрын
will it not work with localhost url while apllying validate
@lovarajugudivada Жыл бұрын
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.
@shubhamthorat57573 ай бұрын
when your previous token gets expired then it show error
@sanjaydavey53 жыл бұрын
@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?
@monalikazamader51795 ай бұрын
While hitting the /token endpoint , I am getting method not allowed for endpoint error, please help..
@shubhamthorat57573 ай бұрын
You need to apply by POST
@sunilmuki4 жыл бұрын
I'm new the Mule, In API Manager what did u deployed? could you explain that steps.
@sahilsharma35274 жыл бұрын
Object store life is for 30 days. Does that mean our client ids will get deleted after 30 days?
@shivangisingh2440 Жыл бұрын
I also have same question will our api's get deregister after 30 days ?? @sahilsharma3527 Let me know if u got any idea on this
@mahesh08153 жыл бұрын
Hi Jitendra, I have seen your video and practiced. But I am facing no access token was received. How to solve it?
@shubhamthorat57573 ай бұрын
first at the endpoint give /token instead of your endpoint. with post then you get the token
@lavanyamailz14 жыл бұрын
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 .,
@MrPmmelvin4 жыл бұрын
Same for me. Can someone help on this issue
@lavanyamailz14 жыл бұрын
Melvin this works for me, ttl 120 seconds, expiration as 30 mins in token object store settings , try it . It worked for me
@MrPmmelvin4 жыл бұрын
@@lavanyamailz1 Hi but this works only in local machine. When it is deployed to cloud hub the ttl is getting override to 86400seconds
@lavanyamailz14 жыл бұрын
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
@lopintipriya35104 жыл бұрын
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 ..?
@06n21a05113 жыл бұрын
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.
@shashiranjanv5 ай бұрын
Thannk you
@SatheeshkumarKaramala Жыл бұрын
Hi sir where do we get client id and client secrete?
@shubhamthorat57573 ай бұрын
Its a random. but if you wants to generate it there are lots of algorithms.
@waretejuwolf4 жыл бұрын
Hi, Do you have any video? explaining about the password grant type. I have been looking for it.
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?
@ravithorwe11594 жыл бұрын
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"
@muletechnologyacademy-zero56254 жыл бұрын
You need to provide correct client I’d and secret
@saggawde14 жыл бұрын
Thank you
@sheetalray60212 жыл бұрын
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?