Now, in this lecture, let's try to create an outline, details on the Keat Luxo so that I can use
those plain details inside my angular application.
So for the same, I have to click, clanked and create a client.
So client 80 IQ is easy public client.
So this is my client I.D. and clicking seal.
The very first note that I had to make for this client is to make sure that access type is public.
So, Veneri, you have access type as public, then you are Keek.
Luxo knows that there is no secret associated for this.
And it and it will follow Bekesi method kind of operation called Grantville.
And also how to make sure standard flow enabled is on, because this is the attraction code grant flow
and coming to redirect you are a winner after login inside our EASI Bank UI application, the user has
to land it on the dashboard page.
So due to that reason, I'm giving the value redirect you are as local host to four thousand two hundred
dashboard.
So this is the port where my henggeler application will be deployed.
So I have mentioned the same under redirect to wartell, which is slash dashboard.
This will make sure my user lands on to the dashboard of the logging operation is successful.
And one more last configuration that I had to do is click on these advanced settings and are Prosky
for Gornick Cent, which is Bixi.
I have to select, yes, 256.
So this is the cryptographic encryption algorithm that my UI application and geek like server can follow.
To understand the code verifier and how code challenges data are based upon the code verified, we can
also use plain but plain is pretty unsecure way.
So due to that reason, I'm selecting, yes, 256.
Once we make this change, we can click through.
And if we go to the top, you can see there is no credential stop.
The reason is this a public facing client and there is no need of credentials.
We should only pass the client data and core to challenge during the first interaction with the key
closo.
And once the attrition code is received, then we should pass the client I.D. along with the quarter
verified.
And if the court verified and court challenges matches with the expectation that my Clerk Sarwari is
expecting, then the user will get a successfully access token.
So now we created successfully a public facing line.
Details on the key blocks of what?
And coming to the user.
We don't have to create a separate user again.
We can use the same user because user details, nothing have changed regardless of what approach you
choose.
Because the expectation from the user is always to enter the user name and password.
So due to that design, we can use the same user that we created before.
So with this, we all set to test the attraction called Grandcolas with the Pixy inside angular application.
Thank you.
And I'll see you in that next lecture.
Bye.