Before we go ahead and implement or to alteration and identification framework, inside are easy bank
Web application, let's try to spend a few minutes on what is opening reconnect.
So you might be hearing a lot about and reconnect from your colleagues.
Friends, are any blogs that you might be reading and wondering what is open and reconnect and how it
is related to auto framework.
So both auto and open.
They are very similar with the minor difference.
The differences openly connect is built on top of auto framework to provide identity details of the
user for whom we are issuing an access token like without opening reconnect long Baccarin auto framework
is introduced in the industry.
Many organizations, they started implementing it, and the main purpose of auto framework is only to
implement authorization based upon access management and role management.
And since there is no standard way of sharing identity details of the user, every auto server implementation,
they used to have their own way of sharing the identity details of that user.
So to address those challenges related to non-standard ways of sharing identity, details between observer
and client applications in new protocol is built on top of auto framework.
So Open-Ended Kanaks provides authentication by introducing a new ID token, which contains user details
with the new set of scopes and claims specifically related to identity.
So just like how or to framework is giving access token, if you incorporate any authentication server
which is leveraging open a reconnect.
It will give you two types of tokens.
One is an access token, which is from the auto, and the other one is an I.D. token, which is from
the open reconnect.
And this I.D. token will how identity details of the user like his email, like his profile details.
So all those details are standardized and kept inside the ID token.
So if you can see the diagram here first, what framework is built on top of his QTIP protocol?
And the main intention of the auto framework is to provide alteration of the user.
Like it will give you an access token based upon the access token.
It will identify whether a given user can access a particular resource are not.
But the limitation that we have it all to framework is where there is no standardized way of knowing
to whom that access token is belong.
That problem is solved by open reconnect.
So on top of war two, we also have open and reconnect built.
And that will focus on authentication, which will share the I.D. token that contains all the details
of the identity of the user who is trying to get an access token.
So now we know what is open and reconnect.
Let's try to understand why openi reconnect is very important, since many of the Arab nations they
started incorporating WATU framework and many and many of the application they're trying to interact
with each other by leveraging access token provided by the authorization.
So there are needs to know to whom this access token belongs to.
So that's where identity came into picture.
And identity is the key to any application.
So with this identity putting inside or to framework, along with the access token, a new paradigm
came into picture, which is i'im identity and access management strategy like we know or Pinetti handles
with identity and authentication and authorization handled with the access management using rules and
authorities.
If you clap both of them, you will get a new strategy, which is identity and access management.
So along back, many of the big organizations, they already moved to that open connect.
And even if you go and leverage any products that are available, like autarkic Gloc, they are leveraged
already openly.
That's why we're discussing about opening iConnect now.
So don't confuse between open ended and auto.
So to framework will help you with an access token if your organization doesn't need any identity details
in a standardized way.
Then you can go and happily live with auto framework.
But if there is a need to know the identity of the user, then definitely go ahead and implement open
and connected based authentication and authorization framework.
So whenever I can start to open, reconnect, I also get auto framework.
The reason is open connect to beat on top of auto framework.
So it is very simple.
Open-Ended connect value to tokens.
One needs access token and the other one is identity token.
Whereas if you implement only or to framework, you will get only access token.
So if you really ask me what is present inside my token, is it will how user details like your email
address his first name.
All those details can be incorporated inside hidy token and openly connect users JWT standard in order
to generate a Islay token.
And at the same time, when you incorporate opening connect, it will have a dedicated standardised
API endpoint UALE with the name slash user info, which can be invoked by client applications if they
want to know more about user details.
So this will open and connect brings more transparency in to identification and automation.
So don't worry.
We are going to discuss this in practical using Keek Laakso.
And during that time, it will make more sense to you, Fano.
Please remember that open already built on top of auto framework and it provides added token along with
the access token with open reconnect.
We are moving to a new strategy called Identity and Access Management.
Thank you.
And I'll see you in that next lecture.
Bye.