1 00:00:00,360 --> 00:00:07,710 Now, in this lecture, let's try to explore on how to get an access token from the key clocktower and 2 00:00:07,710 --> 00:00:12,120 pass on that access token to the resource of what to get the proper response. 3 00:00:12,600 --> 00:00:19,310 So in order to get an access token from the KIC Luxo, I should know what is the endpoint you are on 4 00:00:19,320 --> 00:00:23,940 that I need to invoke against my cheak Luxo to get an access token. 5 00:00:24,210 --> 00:00:29,480 So you're not to know all the endpoint duodenal supported by you are Kikla. 6 00:00:30,540 --> 00:00:34,500 You can invoke rest API call for that. 7 00:00:34,500 --> 00:00:38,120 You are a local host at last. 8 00:00:38,190 --> 00:00:38,910 The Yelp's. 9 00:00:39,090 --> 00:00:40,470 And what is the real name? 10 00:00:40,740 --> 00:00:41,400 Dot. 11 00:00:41,670 --> 00:00:45,540 Well, hyphen known slash openi reconfiguration. 12 00:00:45,870 --> 00:00:54,120 If we invoke against this you are and you will get all the APIs supported by you are key Glock's, Glatzer. 13 00:00:54,450 --> 00:00:58,980 And also it will give you what kind of grant types that support it. 14 00:00:58,990 --> 00:01:03,870 Support operation called implicit refresh, token password, client credentials. 15 00:01:04,290 --> 00:01:06,360 So all the details it will provide. 16 00:01:06,840 --> 00:01:12,990 But we want to understand what is the endpoint you are told that we need to invoke in order to get an 17 00:01:12,990 --> 00:01:18,030 access token in the claim to current credentials grant type for the same. 18 00:01:18,210 --> 00:01:20,640 You can see there is a token endpoint. 19 00:01:21,120 --> 00:01:24,360 So this is the endpoint to all that you harpic invoke. 20 00:01:24,660 --> 00:01:29,070 So localhost, 880 arterials, what is the real name protocol? 21 00:01:29,370 --> 00:01:29,810 Open. 22 00:01:29,820 --> 00:01:31,470 It connects last token. 23 00:01:31,740 --> 00:01:36,540 So we have to take this endpoint to order and paste it here. 24 00:01:36,840 --> 00:01:39,450 It has to be a post to API invocation. 25 00:01:39,780 --> 00:01:46,620 So here under Bardy, we have to pass clean, tidy Glines secret. 26 00:01:46,860 --> 00:01:49,710 What is the scope and what is the grant type? 27 00:01:50,040 --> 00:01:54,810 You're not Lineberry is the idea that we created in the key Glock's or what? 28 00:01:55,440 --> 00:02:02,250 So if you go and see the claims available inside Quique log, we created an Landesbank EPA. 29 00:02:02,550 --> 00:02:06,570 So this is the same name that you have to argue here. 30 00:02:06,960 --> 00:02:12,210 And the claim secret, we can take it from the credentials space that we have here. 31 00:02:12,750 --> 00:02:15,240 So I'm just copy pasting that claim. 32 00:02:15,240 --> 00:02:22,560 Secret and scope is optionally since we are using open relativities and one more layer on top of what, 33 00:02:22,560 --> 00:02:23,250 two framework. 34 00:02:23,490 --> 00:02:25,350 By default, we can use open. 35 00:02:25,890 --> 00:02:30,750 Similarly, we can use your email address scopes also. 36 00:02:31,050 --> 00:02:38,280 So all these scopes how different different responsibility inside open Nilekani so open and scope will 37 00:02:38,280 --> 00:02:41,820 do me and access token and ID token. 38 00:02:42,300 --> 00:02:51,090 And I can mention more number scopes also separated by space likes space email space address. 39 00:02:51,420 --> 00:02:58,830 So this yume open area scope details, email details and address details of the user. 40 00:02:59,100 --> 00:03:05,340 And since we are using grant type of client underscore credentials where there is no user involved, 41 00:03:05,550 --> 00:03:08,080 we have Pegu client underscore credentials. 42 00:03:08,100 --> 00:03:17,940 So with all these details present inside the body in an encoded way, we can invoke the EPA after invoking 43 00:03:17,940 --> 00:03:20,550 I'm getting invalidly client credentials. 44 00:03:20,910 --> 00:03:23,700 The reason is we have given invalid client ID. 45 00:03:24,180 --> 00:03:27,210 So the client I.D. is easy bank API. 46 00:03:27,420 --> 00:03:29,730 So let's try to correct that also. 47 00:03:30,000 --> 00:03:36,540 So with this now, I should get an access token ID token from the key Glock's hour. 48 00:03:37,110 --> 00:03:43,980 So now we got a successful access token from the key clerk's over in the next lecture. 49 00:03:44,130 --> 00:03:49,300 Let's try to pass this access token to the resource of Venera. 50 00:03:49,320 --> 00:03:52,500 We are trying to invoke that my account API. 51 00:03:52,680 --> 00:03:53,160 Thank you. 52 00:03:53,160 --> 00:03:54,870 And I'll see you in that next lecture by.