In the previous lecture, we have made some changes inside our application to use the GitHub based workflow
during the authentication and alteration of the application, so we built a simple springboard application,
which has only a single controller, which is secure controller with a pad slash, which will redirect
due to the security team and will display the skill that has to, with the message, successfully log
in using GetUp!
And at the same time, it will also bring to the the basic details that we received from the GitHub
also belongs to the logged in user.
So now let's try to start this application and see how things are working so far that first I'll go
to the main class Springboard class and I'll start this application in debug mode and also keep a breakpoint
here so that we can see what kind of details that we are getting from the get help about the user.
So once the server is starter, we can go to the browser and try to access the only part available inside
this application, which is really since we are accessing this part very first time without logging
in, it should redirect us to the GitHub for proving our identity.
Once GitHub acknowledges our identity and provider access token, then only this application has to
display the protected resource which is secured attached to him.
So in this scenario, I am the resource owner and this application is the resource server.
Azzara is a GitHub client.
Is the this application.
So the same application is acting as both client and the resource server.
So I'm just entering the localhost 88, which is belongs to my application.
As soon as I click enter, you can see since I have not logged in previously, I have been directed
to the GitHub Observer with the client.
I read that I configure and at type as outrace along with the other details like redirect.
You are all those things.
And you can also see this will provide you the client details.
Who redirected to this page.
Like, if you can recall, during the registration of the client details in the GitHub we provided this
spring security board to the same logo that you uploaded will be displayed.
Otherwise, a different logo is being displayed here.
But you have a logo uploaded that that logo also will be displayed here so that you are giving a better
user experience to the resource, one at our user indicating, OK, my login has been deleted by so-and-so
client to the GitHub.
Now I'm authorizing this application, client application to get the resources about my basic details
from the GitHub, like my email login details, repository details which can be leveraged by the client
application.
So now I have to enter my GitHub login credentials.
And this is super safe because I'm right now in the GitHub login page itself, but not on the application
login page.
As soon as I click sign in force, successful authentication happens.
You can see you are being redirected to the outraced application.
But since we kept a breakpoint here, it's keep on rotating and you can see inside the token you will
get all the details of the user inside the principle, like what is the name that is being maintained
in the GitHub?
What are the authorities that has been issued?
User attributes like what is my login inside GitHub?
From which note I'm getting these details.
Norelli is a place where this alteration server has been deployed.
And what is my outargue are like if someone wanted to see what is my avatar?
You are it is also giving that you are all along with the followers.
You are following me and at the same time following you are allowed to identify whom I am following,
followed by what are the repositories that I maintain private repositories, everything you get from
the GitHub.
Since I am requesting GitHub like I am okay to provide these basic details to this client application.
That way GitHub is sharing all these details to them.
So now if you release this breakpoint, you will go and see.
You can see we have been shown the message that is present in the secure that heads to you.
So now if I refresh again, it don't go through that wall to flow and because my application already
has access token, so there is no need for me to get them again.
Access token from the observer.
So in this way we can use the spring security framework to implement or to flows inside our application.
I hope now you have a clear understanding how to implement a.
Ocean floor using our to framework by leveraging the other was available in the industry.
I also applaud the court that we built in this section to this video.
Please download it and refer with what you have been doing along with me for any issues.
But do you have any questions?
Please feel free to post them in the Q&A section.
Thank you.
And see you in the next section.