1
00:00:00,360 --> 00:00:06,810
Now, in this lecture, let's try to explore a few of the out-of-the-box features provided by clock.

2
00:00:07,110 --> 00:00:11,220
The very first one that I want to highlight is about the teams inside key clock.

3
00:00:11,340 --> 00:00:17,320
So if you go and see our login page by default, I didn't code anything to appear like this.

4
00:00:17,400 --> 00:00:22,140
So this is coming from a team that is by default construct by the Kikla.

5
00:00:22,170 --> 00:00:27,450
So these loggin teams, you can identify and real settings if you click real settings.

6
00:00:27,600 --> 00:00:33,540
There is a tab teams here for each and every process that we can do inside Kikla.

7
00:00:33,540 --> 00:00:39,660
Like we can define a team like for logging that can be for any team account I can do for any team admin

8
00:00:39,660 --> 00:00:42,750
console, how it should look like I can define a team.

9
00:00:42,990 --> 00:00:49,200
Similarly, Geek Gignac also capable of sending emails like one note an account is created, password

10
00:00:49,200 --> 00:00:52,800
expert or password is changed for all those e-mails.

11
00:00:52,830 --> 00:00:57,660
Also, we can create a team that is specific to your organization, Fano.

12
00:00:57,690 --> 00:01:02,670
By default, Kikla is considering the Kikla team that is available for login.

13
00:01:02,880 --> 00:01:07,320
So if you click on that teams available, there is a basic theme and key CLOC team.

14
00:01:07,500 --> 00:01:11,040
Let me see how it will look when I select the base.

15
00:01:11,160 --> 00:01:12,870
So now I'm clicking save.

16
00:01:13,050 --> 00:01:18,750
So if I go to the page of my homepage of Angular app, if I click login.

17
00:01:18,930 --> 00:01:21,300
So this is how the best team looked like.

18
00:01:21,450 --> 00:01:28,050
So the best team will not have any success or any beautification done for your login page.

19
00:01:28,410 --> 00:01:34,470
But as soon as I change the login team to kick lock and save it, if I try to reload again, you can

20
00:01:34,470 --> 00:01:39,180
see my login page has a team now with the name Key Club.

21
00:01:39,480 --> 00:01:44,280
So for some reason, if you want to maintain your own team, your own login page.

22
00:01:44,370 --> 00:01:50,970
So that user doesn't have to feel like he's getting redirected to some other server, then definitely

23
00:01:51,150 --> 00:01:57,000
you have an option of building your own teams based upon your own heads, HTML contents, users, content,

24
00:01:57,210 --> 00:01:58,020
images.

25
00:01:58,170 --> 00:02:01,800
So all those things, you can build your own team.

26
00:02:02,100 --> 00:02:05,610
Once you build your own team, you'll get an option here to select.

27
00:02:05,850 --> 00:02:11,340
But if you really have that scenario where you have to build your own team for your organization, I

28
00:02:11,340 --> 00:02:18,840
will request go to this documentation page of Kikla Lugnut Orji and look for the teams section here.

29
00:02:19,170 --> 00:02:22,860
They have a clear explanation how you can define your own teams.

30
00:02:22,860 --> 00:02:24,390
How can we configure them?

31
00:02:24,750 --> 00:02:27,030
How can we create a team, deploy them?

32
00:02:27,390 --> 00:02:29,550
So all those details are mentioned here.

33
00:02:29,820 --> 00:02:35,130
Now, moving on to the feature client, Scope's, like we were discussing previously, when we are making

34
00:02:35,130 --> 00:02:41,640
a request to Kikla, we used to mention the scope like openly email profile.

35
00:02:41,910 --> 00:02:48,360
So these KORPS will help us in getting the details that we are expecting inside the JWT token.

36
00:02:48,660 --> 00:02:55,250
Like you can see by default, Key Gloc has address email, phone profile roles.

37
00:02:55,260 --> 00:03:01,260
So there are many clayne scope created for us by default and E to scope if you click on them.

38
00:03:01,260 --> 00:03:07,800
Like if I click on email, you can see what kind of details I get when a request for this scope.

39
00:03:08,010 --> 00:03:12,660
So for email scope, Algate, what is the user email whether his email is verified?

40
00:03:12,840 --> 00:03:17,250
Similarly for Adres, if I check, I will get the user address details.

41
00:03:17,520 --> 00:03:21,630
You can also check the phone client scope here and get phone number verified.

42
00:03:21,630 --> 00:03:25,350
And his phone number is available inside his profile.

43
00:03:25,650 --> 00:03:28,200
And at last, let's check profile also.

44
00:03:28,380 --> 00:03:29,760
And that profile you can see.

45
00:03:29,920 --> 00:03:33,720
You'll get a lot of details of the user like full name picture what John.

46
00:03:33,720 --> 00:03:39,720
He's presenting to website, family name, given name, birth date, gender nickname, user name, updated

47
00:03:39,720 --> 00:03:40,020
date.

48
00:03:40,140 --> 00:03:44,800
So every details about him, you will get under profile scope.

49
00:03:45,090 --> 00:03:53,160
And by default, Quick Log will provide this course for every client application that is distributed

50
00:03:53,430 --> 00:03:55,290
like any client application.

51
00:03:55,300 --> 00:03:56,160
Who do you start with?

52
00:03:56,160 --> 00:04:03,840
The clock so they can request your email profile roles, address phone number, profile details.

53
00:04:03,840 --> 00:04:08,140
All these KORPS by default are granted to the client applications.

54
00:04:08,430 --> 00:04:14,640
But if there is a scenario where you want to create your own scope, customize the scope, you can create

55
00:04:14,640 --> 00:04:20,130
that scope, and you can define what kind of details the key clock has to share to the client.

56
00:04:20,459 --> 00:04:25,560
And similarly, you can also control which a client can get within the scope.

57
00:04:25,560 --> 00:04:33,510
Details like if you go and Check Ezy public client for client scope, you can see by default all the

58
00:04:33,510 --> 00:04:34,520
default clients.

59
00:04:34,530 --> 00:04:41,280
Kobzar, assign you file removal like any email or profile from this location.

60
00:04:41,580 --> 00:04:49,320
Then this easy public client cannot request the scope of your email and they will get an error.

61
00:04:49,530 --> 00:04:56,450
So that kind of control also you will get inside identity and access management products like Gloc.

62
00:04:56,790 --> 00:04:59,610
Similarly, by default, we are sharing the rules also at.

63
00:04:59,740 --> 00:05:05,680
Address, phone number, everything we are sharing for note to the client applications, but you can

64
00:05:05,680 --> 00:05:08,620
control also based on your custom requirement.

65
00:05:08,920 --> 00:05:14,950
We saw water rolls coming to identity providers using identity providers.

66
00:05:15,190 --> 00:05:19,720
We can integrate our login page with social logins.

67
00:05:19,720 --> 00:05:27,850
Also, like I can add on any GitHub, Facebook, Google, LinkedIn, any external identity provider

68
00:05:27,850 --> 00:05:30,550
like Geek Log itself is an identity provider.

69
00:05:30,550 --> 00:05:37,000
But if you want to bring one more identity provider inside a login page of keek log, then definitely

70
00:05:37,000 --> 00:05:38,020
you can bring that.

71
00:05:38,230 --> 00:05:45,340
I will join the next video, How to Integrate GitHub identity provider into Quique Log Login Page,

72
00:05:45,610 --> 00:05:46,810
How easy it is.

73
00:05:47,110 --> 00:05:53,080
But as you can see here, there are many options of identity providers that you can choose, especially

74
00:05:53,080 --> 00:05:59,680
for social logins, right from GitHub to Facebook, Google, LinkedIn, Microsoft, Twitter, PayPal,

75
00:05:59,680 --> 00:06:00,520
Stack Overflow.

76
00:06:00,730 --> 00:06:07,570
So all these identity providers you can choose based upon your request and coming to the user federation.

77
00:06:07,780 --> 00:06:13,600
Sometimes you may have an scenario where all the users are present in certain elab location or Active

78
00:06:13,630 --> 00:06:14,800
Directory location.

79
00:06:14,980 --> 00:06:22,000
So in those Senata, instead of maintaining the users inside Keek Luxo, you can integrate that Elab

80
00:06:22,000 --> 00:06:25,930
or Active Directory with the help of user federation.

81
00:06:26,260 --> 00:06:32,120
And coming to authentication inside authentication, you can define all the rules.

82
00:06:32,140 --> 00:06:35,450
What should happen during authentication process?

83
00:06:35,470 --> 00:06:39,390
What kind of restrictions that you want to put like for password policy?

84
00:06:39,400 --> 00:06:40,420
You can see right now.

85
00:06:40,570 --> 00:06:42,550
I don't have any password policy.

86
00:06:42,760 --> 00:06:48,880
If I tried to add a password policy like where minimum length of the password should be eight characters,

87
00:06:48,880 --> 00:06:56,020
as soon as I say so, this password policy will be enforced by my key clock server for all the users

88
00:06:56,020 --> 00:06:57,910
that are trying to register with it.

89
00:06:58,150 --> 00:07:04,660
So if I try to create an user like example is a user name, I'm just clicking.

90
00:07:04,660 --> 00:07:10,510
So if I go to credentials and if I try to do one, two, three, four, five, one, two, three, four,

91
00:07:10,510 --> 00:07:18,550
five as an password can see, I'm getting an invalid password error and the minimum lente should be

92
00:07:18,550 --> 00:07:18,970
eight.

93
00:07:19,150 --> 00:07:23,860
So let me try to give that arbitrary password like one, two, three, four, five, six, seven, eight.

94
00:07:24,190 --> 00:07:29,620
Similarly for password conformational silu, one, two, three, four, five, six, seven, eight.

95
00:07:29,920 --> 00:07:31,660
And clicking set password.

96
00:07:32,290 --> 00:07:39,010
So here now it got access because my password policies that I have defined, those are getting satisfied

97
00:07:39,340 --> 00:07:41,890
because I choose a password of eight characters.

98
00:07:42,020 --> 00:07:48,070
And we saw like water users, how we can create all the users, how we can see them.

99
00:07:48,430 --> 00:07:53,050
Similarly, we can also create grouping like I like means all supervisors.

100
00:07:53,320 --> 00:07:57,610
So those kind of groups also we can do inside key blocks over.

101
00:07:57,970 --> 00:08:02,410
So this way there are many out-of-the-box features provided by cheak.

102
00:08:02,410 --> 00:08:07,810
Lots of words on mine since that request is whenever you want to know more about Kikla features that

103
00:08:07,810 --> 00:08:08,740
it is provided.

104
00:08:09,040 --> 00:08:16,360
You can go to the document speech of cheak log dot org and you can explore all the documents so that

105
00:08:16,510 --> 00:08:17,950
it will give you more details.

106
00:08:17,950 --> 00:08:22,120
And with the help of documents you can easily make changes.

107
00:08:22,330 --> 00:08:26,800
Are custom additions to your key clocktower based upon your custom requirements.

108
00:08:27,100 --> 00:08:27,580
Thank you.

109
00:08:27,820 --> 00:08:34,750
In the next picture, let's try to integrate Git hub login option inside our quick log login page.

110
00:08:34,990 --> 00:08:35,539
Thank you.

111
00:08:35,559 --> 00:08:37,210
And then assume that next lecture by.