Now, in this lecture, let's try to explore a few of the out-of-the-box features provided by clock.
The very first one that I want to highlight is about the teams inside key clock.
So if you go and see our login page by default, I didn't code anything to appear like this.
So this is coming from a team that is by default construct by the Kikla.
So these loggin teams, you can identify and real settings if you click real settings.
There is a tab teams here for each and every process that we can do inside Kikla.
Like we can define a team like for logging that can be for any team account I can do for any team admin
console, how it should look like I can define a team.
Similarly, Geek Gignac also capable of sending emails like one note an account is created, password
expert or password is changed for all those e-mails.
Also, we can create a team that is specific to your organization, Fano.
By default, Kikla is considering the Kikla team that is available for login.
So if you click on that teams available, there is a basic theme and key CLOC team.
Let me see how it will look when I select the base.
So now I'm clicking save.
So if I go to the page of my homepage of Angular app, if I click login.
So this is how the best team looked like.
So the best team will not have any success or any beautification done for your login page.
But as soon as I change the login team to kick lock and save it, if I try to reload again, you can
see my login page has a team now with the name Key Club.
So for some reason, if you want to maintain your own team, your own login page.
So that user doesn't have to feel like he's getting redirected to some other server, then definitely
you have an option of building your own teams based upon your own heads, HTML contents, users, content,
images.
So all those things, you can build your own team.
Once you build your own team, you'll get an option here to select.
But if you really have that scenario where you have to build your own team for your organization, I
will request go to this documentation page of Kikla Lugnut Orji and look for the teams section here.
They have a clear explanation how you can define your own teams.
How can we configure them?
How can we create a team, deploy them?
So all those details are mentioned here.
Now, moving on to the feature client, Scope's, like we were discussing previously, when we are making
a request to Kikla, we used to mention the scope like openly email profile.
So these KORPS will help us in getting the details that we are expecting inside the JWT token.
Like you can see by default, Key Gloc has address email, phone profile roles.
So there are many clayne scope created for us by default and E to scope if you click on them.
Like if I click on email, you can see what kind of details I get when a request for this scope.
So for email scope, Algate, what is the user email whether his email is verified?
Similarly for Adres, if I check, I will get the user address details.
You can also check the phone client scope here and get phone number verified.
And his phone number is available inside his profile.
And at last, let's check profile also.
And that profile you can see.
You'll get a lot of details of the user like full name picture what John.
He's presenting to website, family name, given name, birth date, gender nickname, user name, updated
date.
So every details about him, you will get under profile scope.
And by default, Quick Log will provide this course for every client application that is distributed
like any client application.
Who do you start with?
The clock so they can request your email profile roles, address phone number, profile details.
All these KORPS by default are granted to the client applications.
But if there is a scenario where you want to create your own scope, customize the scope, you can create
that scope, and you can define what kind of details the key clock has to share to the client.
And similarly, you can also control which a client can get within the scope.
Details like if you go and Check Ezy public client for client scope, you can see by default all the
default clients.
Kobzar, assign you file removal like any email or profile from this location.
Then this easy public client cannot request the scope of your email and they will get an error.
So that kind of control also you will get inside identity and access management products like Gloc.
Similarly, by default, we are sharing the rules also at.
Address, phone number, everything we are sharing for note to the client applications, but you can
control also based on your custom requirement.
We saw water rolls coming to identity providers using identity providers.
We can integrate our login page with social logins.
Also, like I can add on any GitHub, Facebook, Google, LinkedIn, any external identity provider
like Geek Log itself is an identity provider.
But if you want to bring one more identity provider inside a login page of keek log, then definitely
you can bring that.
I will join the next video, How to Integrate GitHub identity provider into Quique Log Login Page,
How easy it is.
But as you can see here, there are many options of identity providers that you can choose, especially
for social logins, right from GitHub to Facebook, Google, LinkedIn, Microsoft, Twitter, PayPal,
Stack Overflow.
So all these identity providers you can choose based upon your request and coming to the user federation.
Sometimes you may have an scenario where all the users are present in certain elab location or Active
Directory location.
So in those Senata, instead of maintaining the users inside Keek Luxo, you can integrate that Elab
or Active Directory with the help of user federation.
And coming to authentication inside authentication, you can define all the rules.
What should happen during authentication process?
What kind of restrictions that you want to put like for password policy?
You can see right now.
I don't have any password policy.
If I tried to add a password policy like where minimum length of the password should be eight characters,
as soon as I say so, this password policy will be enforced by my key clock server for all the users
that are trying to register with it.
So if I try to create an user like example is a user name, I'm just clicking.
So if I go to credentials and if I try to do one, two, three, four, five, one, two, three, four,
five as an password can see, I'm getting an invalid password error and the minimum lente should be
eight.
So let me try to give that arbitrary password like one, two, three, four, five, six, seven, eight.
Similarly for password conformational silu, one, two, three, four, five, six, seven, eight.
And clicking set password.
So here now it got access because my password policies that I have defined, those are getting satisfied
because I choose a password of eight characters.
And we saw like water users, how we can create all the users, how we can see them.
Similarly, we can also create grouping like I like means all supervisors.
So those kind of groups also we can do inside key blocks over.
So this way there are many out-of-the-box features provided by cheak.
Lots of words on mine since that request is whenever you want to know more about Kikla features that
it is provided.
You can go to the document speech of cheak log dot org and you can explore all the documents so that
it will give you more details.
And with the help of documents you can easily make changes.
Are custom additions to your key clocktower based upon your custom requirements.
Thank you.
In the next picture, let's try to integrate Git hub login option inside our quick log login page.
Thank you.
And then assume that next lecture by.