In this video, we're going to discuss about the application, which we're going to build throughout
this course.
So this is the way of that application and right now it just has only your way and there is no security
implementor and everything.
All the data is Hakata.
There is no back end associated and there is no database associated right now for this application.
Don't worry if you're not comfortable about that, you wait by answering that this application has been
developed using angular.
I'll be also sharing this.
You go through your GitHub link, you can always download from the top and only concentrate on the backend
security code that we are going to build toward this.
This is an application related to bank and the reason why we choose the banking domain, each answering
that security is most important for any banking application.
So if you see the very first landing page that the customer of a bank will be shown is a login page
user once enters the email and password associated with his or her account, which should be authenticated
and authorize the user using a back in service leveraging this spring security frame.
Once the user is logged in and authorized, we should show the user dashboard where he has various sections
about his account, details and balance associated with his account.
What the transactions that he has performed in the past few days, loans associated and cards that he
has associated with that bank.
So all these four sections like account balance loans cards has to be because these are the rest of
it service or any backend services which the UAE will call by passing on the authentication details
to.
We should make sure all this Forest Service has to be secured at any point of time and the user should
be able to access this dashboard page only once he authorized and authenticate himself.
And at the same time, we have free form of pages like contact us with the bank, want anyone to access
this?
There is no security restriction on this because obviously in a case where a non customer of the bank
or any public person want to contact the bank, this page will allow them without entering his credentials.
That's where we have to make sure we build a back.
And so is accepting the request from this page without any security details associated with it.
And at the same time, we have a notice, a space where bank regularly publishes about that important
announcements to their customers, public, everyone.
So that's where obviously this page also has to be free from any kind of security.
And all this notices has to come from a bank.
And so we also build the notices some ways, which is doesn't require any security and anyone can access.
So on a high level, I'm assuming you understand there is a login page and contactors.
I'm noticing speech which anyone can access without entering their credentials.
At the same time, once the user is logged in, we should be able to navigate to dashboard where he
or she can again call more services as opposed to the account balance loans cards and what the user
want to click logout.
He can always post this, quote, link and go back to the login page.
This is what we are going to build on a high level.
And if you see there is no security associated with it, we will focus right now in the coming reviews
on the back and how to build up the services associated for all these features, how to protect a few
of them and how to make them available for anyone to will do all such configurations on the backend
to funnel ECDIS an input as a requirement for a project that we are going to build will come to the
Web.
But again, once we build all the backend equipped for this, I hope that makes sense to you.
Thank you.
And get you in the next review by.