Like we're discussing in the previous lecture, we had to create and claim to details and the user details
so that we can start leveraging them inside what framework that we are going to implement in the scenario
where like a Web application trying to invoke the EPA's present inside that resource, someone.
So far the same.
I came to the admin console.
The real mechanism is a bank do.
So I'm just clicking clients.
So I'm trying to create a new client.
That's why I'm clicking create here.
So here claim to I.D. I will give you easy UI client.
And definitely this also has to be open and reconnect and then click sale.
So here we have to be very careful while choosing the options.
Since we decided we have to use authorization code, a grant type, it is by default enabled, which
is standard flow enabled.
So you can see here this is the one which supports authorization, court of law, grant type insight
or to framework and definitely access type should be confidential because you'll have a client daily
and client secret.
So with this convocations, we should be good.
But we just have to add value redirect.
You are also.
For now, I'll just mention his sample redirect.
You are evictees.
History type.
Local host.
Eighty eighty one SLAs sample.
So it can give you any redirect.
You are fano.
But in real world scenario, this is that important configuration that you had to configure properly.
The reason is you are quick.
Luxo will redirect the user after providing an access token to that redirect page.
So this is the page which will stop hackers from hacking the access token, because by mentioning the
redirect, you are you are bringing back the user from the key clock or to server page to your own server
page.
So that's why valid redirect uara is very important for now.
I just configured localhost 88 one sample.
So with this, we should be good with all the default configurations.
I'm just clicking save here and I should have got credentials also.
So we have credentials.
Now, we created a successful client that I can use during or to operation code grant type.
So now I knew end user also.
So I'll create our user here.
User name alue accounts.
E-mail is accounts aderet easy bytes dot com.
So the first name is account's.
Last name is Easy Bytes.
So here you also have an flexibility whether user should be enabled or disabled.
Like if you have a scenario where you want to disable and user, you can use this feature to enable
and disable by toggling it.
Ah, you can also do that by invoking rest APIs exposed by the key clock.
So for now, I am keeping the user enabled and email verified.
Also, I'm keeping.
Yes.
I also have an option of adding him to a group.
But for now, I don't want to add to any group.
I'm just clicking sale.
So once that user is created, you can go to credentials to set a password, which can be used as a
temporary or permanent ways.
So I'm just setting a password one, two, three, four, five.
So this password, I don't want to be temporary.
I want to be permanent.
If you keep temporary, it will force the user to change it whenever they're trying to log in very first.
So now, since it is five, just only for testing, I just disable the temporary do off and roll mapping.
Also, we can give.
So we have two types of rules, admin and user.
So I'm just selecting add selector and I assign roles also to the user that I have created, just no
witness accounts.
So we can go and see all the users created, which is accounts like these are all the details that we
provide a user name, email, first name, user name, email, verify.
I'm Karen Schultz.
Also, we said one, two, three, four, five previously.
But if we want to change again and again, you can come on to the page and change role mappings will
allow you to assign roles to the user.
So this way we created a client and user details which we can use during attrition to grant a flow in
the next lecture.
Let's try to leverage this claim details and user details and test the or to authorization code grant
type foster with the posthuman post that we can start integrating that with then Web application.
Thank you.
And then see you in that next lecture by.