#springboot
#java
#microservices
#google
#microsoft
#java
#microservices
#microsoft
Category
🤖
TechTranscript
00:04:30So welcome to the Demo 3.
00:04:33We have completed the Demo 1.
00:04:36In Demo 1, we have seen the course objective.
00:04:39And then Demo 2, we have set our agenda to study the existing application and understanding
00:04:53the requirements.
00:04:54The requirements, then draw the UML class diagrams, then technical architecture, then functional
00:05:01architecture, and microservices overview, again microservices architecture, and migrating
00:05:08strategies from the existing system to microservices architecture, finally the production topology.
00:05:13So this is what we have seen in this introduction to vShopify platform application section.
00:05:20Okay.
00:05:22So yesterday we have seen the users, user management, right?
00:05:29So in the existing application, the business has been classified, the users as two types of users.
00:05:40One is the backend application users or back office users.
00:05:47Second one is the customers.
00:05:48Second one is the customers.
00:05:52So the back office users and then the customers have the different registration flows.
00:05:58So when it comes to the back office application, there will be a super admin who is a configurable
00:06:06user.
00:06:07That means during the application startup, this user will be created in the DB and then this
00:06:14user will be ready to log into the system.
00:06:19That means to the application.
00:06:20When this user will be logged in, then this user will be able to create the other users
00:06:27who are called as the admins and then non-admin users, right?
00:06:33So before this user creation, roles also will be configurable or roles to be also created during
00:06:42the application startup.
00:06:44So this users have a different flow of registration.
00:06:49And then the customer will have a different flow of registration.
00:06:53Yesterday, we have seen this user management registration, how the users will get registered.
00:06:59There will be no notification will be sent, no notification, right?
00:07:04Now let us see the customer management in user management.
00:07:11We have seen the user management.
00:07:12Now let's see the customer management.
00:07:15So today we will see the customer management.
00:07:17So let me start the application.
00:07:21So the applications are running.
00:07:25Customers will be self-registered from the front-end application.
00:07:30So front-end application, what number is 8081.
00:07:34So as soon as we access this app, there is a register button, a register link.
00:07:39So when the user clicks on the register link, the registration page will be opened.
00:08:00So now let us draft the use case of the user management.
00:08:07In the user management, let us draft the use case for the customer, user type of customer.
00:08:15So this is a user management piece.
00:08:17And so let me take one.
00:08:22The row below.
00:08:23Yes.
00:08:25The first one is what?
00:08:26User-vsharpify-platform-user management.
00:08:34platform users management so this is the first module or we can say service one
00:08:47vshapify platform users management so what is this actually so let's try it vshapify
00:08:59platform users were classified as classified as number one back-office users and number two
00:09:15customers customers so what is the difference back-office users not backup back-office
00:09:29users so back-office users what is the job of this back-office users
00:09:35back-office users will be created by the super thing and they can be and they can be admin and
00:09:52non admin users right so who will who will works in the back-end who will works in the back-end who
00:10:16will works in the back-end to upload the let's say to upload the products info to update the discounts
00:10:31right and to create the apply coupons etc so these jobs will be do by whom the back-end people so
00:10:46once the back-end people are the back-office people we can say so we have two applications right so
00:10:53this is the front office application which will be accessed for the customers and then the customers
00:11:00will purchase the products they'll place the artists right and we have the another application called
00:11:09vshapify platform this is the back-office application so let's say let me log in into this back-office application
00:11:21yes this is the back-office application now in this back-office application different users
00:11:38will log in for example there is a user called salesperson so let's take one more incognito window
00:11:50and then let's log in the sales user of course let me do a logout so vshapify salesperson
00:12:06maybe this person's password is
00:12:20no so here if you can see there is no forget password facility so this forget password facility we need to enable actually however let us
00:12:25do one thing let us go to the admin side and
00:12:55so vshapify salesperson so vshapify let us try to edit let's say vshapify admin and then the
00:13:02yeah so yes we can update the password let me update
00:13:11let's use a thread 123 save so i updated the password now as soon as the password is updated
00:13:23let's try to log in let's try to log in to the system with the salesperson
00:13:30so go here and login with the salesperson
00:13:38so vshapify so vshapify iphone sales at the rate
00:13:45ybook email dot com and then the test user at the rate
00:13:50so user is disabled oh my bad user is disabled let's enable the user okay now the user is enabled so once the user is enabled then we should be able to log in that user
00:14:05perfect now the user has been logged in right so this functionality we need to achieve right it was already there in the existing system so in the new microservices architecture also the same functionality we should have to be achieved and if we can observe the dashboards of the super admin and the user
00:14:12the dashboard of the salesperson there is a very limited access to the user and then the user has been logged in and then the user has been logged in
00:14:19right so this functionality we need to achieve right so it was already there in the existing system so in the new microservices architecture also the same functionality we should have to be achieved and if we can observe the dashboards of the super admin and then the dashboard of the salesperson there is a very limited access to the user
00:14:40you can only access the products customers shipping rates orders sales report that's it he is not able to access the brands he is not able to access the users he is not able to access the articles settings no nothing so if you want to update the payment gateway let's say i want to update the paypal payment gateway url and all it's
00:15:09the salesperson can't do because he is not able to see that one only the admin user can receive that means our back rule-based access control we need to implement so let us write all these things as our use cases okay so first i believe this document is okay but let us write the separate documents for the separate use cases fine hope you are following
00:15:37so what is the what is the module so what is the module so what is the what is the module so the module is the user management so use case user management so when the user will be created permissions for sales for shipper so this is what the use case
00:16:05use case use case user management so let me uh you know create a document for each and every use case uh we shopify platform we shopify platform docs
00:16:25uh use case user user skills um user management use case uh perfect so let us update this nodes
00:16:38user management so we shopify platform users are classified as the
00:16:50so we shopify users are classified as the back office users and then the customers both so back
00:17:01office users and then the customers so what is the meaning of this back office users the back
00:17:11office users are the users who will be logging to the back-end system so this one this is the
00:17:18application which is the back-end system what are the products we create here those products
00:17:23will be visible to the front-end users like customers so here is the here is the customer
00:17:32so this customer can see the once he he registered so let's say let's log in maybe I can log in with
00:17:43my credentials yes once the customer is logging the customer is able to place
00:17:53the orders by viewing the products so the products will be visible to here the products will be
00:18:00visible to the users here once the products will be created by the back-office users in the back
00:18:07office application and then the product details product descriptions right so for example we were
00:18:15so there's a product so we can see the details about the product so product name product price
00:18:22description images and details right and then the shipping details shipping cost basically so based
00:18:31on the dimensions of the product the shipping cost will be there right so this is what the product
00:18:37details whether any discount is is available or not coupon codes are available or not so this is what
00:18:43the product details so all these details will be visible to the end customers when only these products will be
00:18:51created and then published right the product will have a life cycle product creation product review product publish
00:18:59we'll discuss when we go for the product use case okay so these products will be visible to the customers when
00:19:09those will be created when those will be reviewed when those will be published however the the published products can be
00:19:19ordered by the customers so now i think it's very clear uh we have the two two users one is the back office user second one is the front office user so the back office users role i think it is very clear for you right so back office users will be created by the super admin as they can be admin and then
00:19:40admin users who will works in the back office application back office application that is v sharp if i plan for map so this is for our understanding i'm just writing it in the back office
00:19:47back office application back office application that is v sharp if i plan for map so this is for our understanding i'm just writing it in the back office
00:20:01back office application that is so to upload the products info to update the discounts to create the apply coupons etc
00:20:17so who will create super admin will create the users so super admin will create the users like this
00:20:23so now the user size can be created now the users created can be logged into the v sharp platform back office
00:20:29application with their respective roles so as soon as the users uh with the different personas will be logged in
00:20:38here personas will be user roles the dashboards will also be displayed as per the permissions they have on
00:20:45the roles so this is one uh so super admin create the users of the back office application as shown below
00:20:55so when the users here the users the created users the created users
00:21:04that created users will get an email notification email notification with the credentials
00:21:11with the credentials with the credentials with the credentials to use to log in the application
00:21:21to log into the application so this is very important point now okay so when the users
00:21:29will be created then for that users the notification will be triggered with the credentials because
00:21:37when the users will be created the credentials will be chosen by the super admin let's see where
00:21:43that facilities is we have in the system so see this create new user yep the super admin can give
00:21:53the password some random password super admin will give then the email will be sent to the user let's
00:22:00say salesman or maybe the ship shipper or whatever the mail will be sent to him then then then the users
00:22:12should have then the users should have to login user should have to be user should have to be
00:22:23verify the email by clicking on the verification by clicking on the verification link but keeping
00:22:37on the verification link so the credential the created user will get an email notification verify
00:22:44email verify email notification with the credentials to use to log into the application
00:22:50notification so then the users should have to be verified email by clicking on the verification link
00:22:58as soon as the user gets verified verified the user account will be enabled and a change password
00:23:14password sorry not change password and a reset password reset password page will be displayed to change the default credentials because you know
00:23:32super admin should not force us to use the credentials what he has given no that is that is called as identity theft
00:23:41super we can use our own passwords we can use we wish of liberty to use the app so no one can
00:23:53theft our identity that's the reason we should have to be display reset password page
00:24:02to change his password or optionally you can go with the same credentials that is the choice there will
00:24:09be skip option also okay so there should be a skip option on the page there should be a skip option on the page
00:24:21if the users wants to continue with the users wants to continue with the default credentials
00:24:33default credentials generated by the super admin got it so this is the use case use case for whom use case for the users
00:24:50okay so the the created users so here we should have to write one more point when the
00:24:56the when the user will be created right then the user will be in the disabled state
00:25:13right disabled state the created users will get an verify email notification with the credentials to use to
00:25:20login to the application so once the verification link will be clicked on then the user identity will be
00:25:28get verified and then the reset password page will be displayed so there should be a skip option also to
00:25:34skip the change password or reset password right so this is what the user management use case and one more point
00:25:45also the disabled users the disabled disabled users should not login the application should not log into the application
00:25:58right and we can also include the multi-factor authentication two-factor authentication not multi at least two-factor authentication
00:26:07what is the two-factor authentication as soon as soon as the as soon as the verify email clicking on the verification link so here
00:26:19as soon as the user gets verified verified then the user account will be enabled and a text message
00:26:28text message text message will be sent the user with some code some code right it's a code and the verify code page
00:26:46will be verify verify page should be displayed
00:26:50should be displayed
00:26:54should be displayed okay so once the okay upon entering
00:27:03upon entering the valid code or valid otp in the verified code page
00:27:11page then the code will be verified
00:27:16then the code will be verified
00:27:20here then the user should have to be verified the email backlink
00:27:23as soon as the user gets it no as soon as the user get verified the account will be enabled no account
00:27:28will not enabled as soon as the user get verified a text message will send now upon entering the valid otp
00:27:36in the verify code page the code will be verified and the user account will be enabled
00:27:47then user account will be enabled and a reset password page will be displayed to change the default credentials
00:27:55this is the perfect flow right so what is here so let me highlight every created user will be in the
00:28:03disabled state this is first point next is what verification email so verify email notification will be sent
00:28:14and next is what uh user gets verified with a text message will be sent to the user
00:28:22right so as soon as the user gets verified a text message will be sent to the user
00:28:27upon entering the valid otp in the verify code page the code will be verified
00:28:31and then the user account will be enabled so this is the next point and there should be a skip option
00:28:39on the page on the what page reset password page there should be a skip option on the reset password page
00:28:47if the user wants to continue with the default credentials so these are all the use cases for the admin
00:28:54you may ask your question sir when the role will be assigned yeah role will be assigned when the user
00:28:59will be created because the role is also choosing here right for a particular job role the entry will
00:29:04be conducted offer will be given accordingly the person will be allocated in that role right so this is
00:29:12what the uh back of back office users back office users use case now front office users okay now the users can
00:29:25create okay okay once once users get verified then the then the then the users can be uh the users can be
00:29:48logged into the vshop if a platform back office application with their respective back office application with their
00:29:54respective credentials that's it not rules with the respective credentials so this is one of the use case also
00:30:03if everything is goes with but the user is not login since that that's not the good thing so
00:30:12this is what the application
00:30:19one moment guys
00:30:19okay so as soon as the users with the different persons will okay once users get verified and the
00:30:34users can be able to log in to the vsharp if a platform back office application with their respective
00:30:40credentials yes as soon as the users with the different persons will be logged in
00:30:44okay this sentence let me refresh as soon as the users will be logged in as soon as the users will be logged in
00:30:57they can see the dashboards
00:31:04based on the based on the different personas based on the different personas
00:31:14the dashboards the dashboards will be displayed the dashboard will be displayed based on the personas
00:31:29persona of the different different personas right as per the permissions they have on their roles
00:31:37so before that there is a role management module also we need to take care of it but this is fine
00:31:54okay so this is these are all what the use cases each and every use case we need to implement and each and
00:32:02every use case meaning each and every point will be will be covered as part of the unit testing okay we
00:32:09should have to test each and everything with the unit testing correct this is java real-time project
00:32:16microservices and react.js class and what we are doing now what i am explaining now
00:32:23how you will do the real-time project without understanding the requirements
00:32:26i don't know guys actually what what is your expectation from the java real-time project but
00:32:40this is what the reality so you may you may without understand the requirement i think most of the
00:32:48guys are habituated to the easier things so we have to complete the things very easily one
00:32:54registration form one login form one dashboard done real-time project is done put your resume
00:32:59attend the interviews that never work out that maybe work out till you will get the offer but once
00:33:05you get the offer once you go inside the company that never works out you have to rely on others you
00:33:10have to break others right for the help so what might mean is you should not be in that position you
00:33:18should be a key player in the team as soon as you will be you know hired you will you will go to the
00:33:25office you should be a key player in the office you should not beg beg the help but that's what the
00:33:33motivation you should have to learn this project and all okay however this is the java real-time project
00:33:42with the react integration class and we are now discussing about the modeling of the system
00:33:50designing of the system system designing phase in system designing we are now understanding the
00:33:57we are now studying the existing system because we're going to migrate the existing system to the
00:34:03microservices nowadays minimum 60 to 70 percent of the projects in the market are the migration projects
00:34:10only the applications might have been written in some other technology then you have to migrate it
00:34:15to the microservices architecture that is the reason i also have chosen the same fashion
00:34:22so as part of it we are now studying the existing system and then connecting the requirements
00:34:28then we will draw the our class diagrams year diagrams human diagrams and all finally we will draw
00:34:34the technical architecture then we will go for the coding so this will be this will be happens
00:34:40before your project starts right so before your project starts already the manager and then the
00:34:49architect will be will be assigned to the project before you guys will be assigned before the developers
00:34:54will be assigned to the project the project will be you know project might have been already started
00:35:01or maybe the architect will go for the requirement analysis and then understanding to the customer's
00:35:05location location and then study the existing system understand the requirements prepare the technical
00:35:12architectures prepare the use cases document then he will come to your workplace and then assign the
00:35:18tasks to you then your team lead will team lead and then manager will take those tasks and then
00:35:24distribute among the team and then make sure those tasks will be deliverable that is the process
00:35:30process without the requirements in the standing i i don't think how you guys will imagine it as a
00:35:36real-time project and i don't know however um oh okay okay yeah yeah yeah really i got your point now
00:35:45correct correct evening it is java uh springwood microservices and morning it is the real-time project i got your
00:35:52intention now yeah yeah yeah um yeah um yeah yeah oh great great i got your point so sorry maybe you
00:36:07know little communication gap i know so sorry i i thought it didn't maybe maybe maybe you are you
00:36:13you misunderstood i thought you might have not concentrating i'm so sorry for that this is something
00:36:18misunderstand happened yeah thanks thanks so yeah i got your point now yeah i got your point yes yes yes
00:36:28so yeah yes sorry for the you know you know misunderstandings and not let us focus on our
00:36:33requirement okay got it fine fine um fine let's let's come on to the mood now okay however uh these are
00:36:40the use cases as soon as the users will be logged in hey don't mind i i thought you know you might be
00:36:46asked in some different perception so don't mind um let's go ahead let's go ahead uh
00:36:56okay uh the evening class is not there actually uh evening evening real-time project batch has been
00:37:03shifted to this morning hours evening we have only the springboard microservices sessions
00:37:09and morning project sessions okay project real-time project i mean in the morning real-time project
00:37:17implementations evening the concept orientation courses yeah okay uh let's come on to the mood now
00:37:27yes so as soon as the users will be logged in they can see the dashboard the dashboard will be displayed
00:37:32based on the different personas and all so uh so i think we can take the screenshots of the dashboards
00:37:40here so let me take the screenshot of the um screenshot of the um super admin and let me take the screenshot of
00:37:55the sales person all right so here is the super admin person we shopify management let me take the screenshot of it um
00:38:09scroll down yes this is the screenshot of the super admin let me just say
00:38:16super admin dashboard screenshot and let us also see the um yeah super admin dashboard screenshot and let us see the
00:38:35normal user right sales person screenshot so that when you are going through the requirements study or
00:38:42requirements understanding you may understand actually by looking into these screens you may understand
00:38:49so this all we need to achieve in the uh react actually so we will do it uh when we do the react
00:38:56integrations so my suggestion guys if any react.js classes are starting then go and then join not only
00:39:03in durga soft but wherever wherever the react.js class are starting you go and then join there those will
00:39:08help you okay so sales personas dashboard sales personas dashboard sales personas dashboard so this is the
00:39:17sales personas dashboard okay sales person's dashboard so based on the role uh the dashboards will be displayed
00:39:26and based on the permissions you can access the things inside the dashboard so again we will discuss about that
00:39:33rollback and then the uh attribute based access management in the authentication module not in the user module
00:39:40okay so this is the uh user registration process so let us say it as the user registration
00:39:49user registration registration
00:39:54registration process so this is the use case for the user registration process
00:39:59process now there will be another use case in the same use case only but the super admin can view the
00:40:07created users edit delete and export the user details in csv and then excel or the pd format whereas the
00:40:15non-super admin users can't see this is again one of the use case one of the constraint like how we have the
00:40:21various constraints here similarly this is also one of the constraints so super admin only can be
00:40:27can be able to see the all the created users but not other other personas so that is very important
00:40:36so super admin only super admin can only can only view the created users edit delete and export the user
00:40:45details in csv excel and pdf formats okay and create user module only enabled for the super admin and then admins
00:40:56create user functionality not body create user functionality only enabled for the super admins or admins
00:41:04but not for the sales persons or the shippers or the delivery persons and all the users can also be
00:41:12searched using the search filter this is also one of the requirement whatever the users created those users
00:41:19should be searchable so such criteria is such criteria are what we need to define right so vshapify
00:41:28platform use that admin role can have the permissions so these are the permissions that the admin role can
00:41:32have this is the permission that the sales person can have this is the permission that the shipper can
00:41:37have and then the editor can have right so and uh here very important uh module is uh exporting the user
00:41:49details in csv and then pdf so let us take it as a separate separate uh point here let me copy this entire
00:41:59and go little down uh here let us at that point so super admin can only export super admin can only
00:42:18generate the report
00:42:22reports by exporting the user details in a csv file or excel file or pdf format file
00:42:30again there will be a different story like uh protecting the pdfs and all that's a different
00:42:35concept but so the the use case is what at least the report should have to be generated
00:42:42fine so that is from the back office users perspective then what about this customer's perspective
00:42:50so customer's perspective also the same one so this is the customers now the customer's use case
00:42:59okay till here guys uh is it clear are any questions or you want any clarity or or you know is it clear
00:43:08so far whatever happened yes yes great great yes downloading excel downloading pdf on every page
00:43:17not on every page mean every grid so if you can see here every grid will have that one so every grid
00:43:25will have so going forward what will come the page later page nations will come so not on this grid
00:43:33actually so this is a common for not on every grid it is it is a common functionality so not on this table
00:43:40actually not on every page only in the page where the users can be seen maybe page nation let's go to
00:43:48the next page only this grid will change because we are using the single page application spa react.js so
00:43:55what will happen only this portion will be displayed with the data the rest of the portions won't be updated
00:44:02so we won't have the export options on each and every every table rather we will have it on the global or general
00:44:15okay got it right yeah okay great um great great now let us see uh let us see the customer management
00:44:27customers customers how the customers will be registered so far we have seen the user registration process for
00:44:33what user registration process of back office users then how it will be in case of the customers the
00:44:40back office users will be created by the super admin right so but the customers will customers will be
00:44:48self self registered users for example uh amazon right you can go and create your account no one will
00:44:55ask you no one will force you you are free but there your identity will be secured that is only the
00:45:01responsibility of the aws platform meaning amazon e-commerce website responsibility is to keep
00:45:10your identity secure that's it apart from that you can log in you can change your mobile you can
00:45:15change your password you can you can log in at any time you can log out you can place the orders
00:45:19you can play it with as per your option so self registration every customer okay customers will get
00:45:29customers will get customers will get uh customers will get created through the self registration process
00:45:42self registration process that means that means um that means the user the users their self the user
00:45:55play itself has to go to the register register link and then then provide the provide the necessary details
00:46:13like as shown below like i shown below remember guys what is the difference between the self registration
00:46:22and then the admin registration right we should have a difference carefully observe now um carefully observe now
00:46:30there is a self registration so in the new system we have to remove these passwords
00:46:39okay in the self registration passwords we should not accept from the farm
00:46:46rather the password should have to be set by him of course now also the passwords are entering by him but
00:46:56we should not keep these passwords in our system until the user identity will be verified that is the constraint
00:47:04right so here one note we should have to write
00:47:07please note that the self sign up self sign up page shouldn't contains shouldn't contains the password fields
00:47:25because until the identity of the user will be verified
00:47:37we should not store the user's password in our system
00:47:46in our system so that is what very very important we should have to always follow the security guidelines
00:47:54we should not breach the security okay so in the new system of course in the existing system
00:48:00uh we are taking the passwords uh we are taking the passwords but in the new system we should not take
00:48:04the passwords so let me you know take a screenshot of it and uh again the same cases will be applied here as
00:48:15that of the as that of the um user's registration right so notifications and all are sending sending
00:48:23sending grid is what we will use to send the email notifications twilio is what we will use to send the
00:48:31sms notifications so free the those who are given some free limitations within that free limitations we
00:48:40will use that api like 100 users 100 notifications per day are free through the send grid and it will
00:48:47you also five text messages per day are free so i think during the demo or during the class is happening
00:48:53we can use them in the free free limits okay then then again this is same when the users will get
00:49:03this is again same so same to same once the user get verified again the same as soon as the users will be
00:49:10logged in till here it is same same process even for the customer as well so when the customer
00:49:22when the customer will be created when the customer will be created then the customer
00:49:28will be in the disabled state the created customer will get a verify email notification with the
00:49:39credentials to use to verify email notification there will be no credentials right so then the user should
00:49:47have to be verified here the customers uh here one more point this verification link will be
00:49:59valid valid valid will be valid for 48 hours only
00:50:08but it was only if the user i mean to say if the customer if the customer can't verify can't verify the email
00:50:23within within this 48 hours
00:50:28the link will be expired automatically and then the customer should have to the customer should have to
00:50:42reach out to the b shopify platform help desk okay this is the case so this is the new functionality
00:50:54when compared to the users this is the new thing now right you can see the difference customer flow
00:50:59and then the users flow so for the users flow there will be no expiry of the verification link they can
00:51:07explore because they were onboarded they were hired they were the employees of the v shopify platform
00:51:12but for the customers it's not like that customer identity is very very important to us so verification link will be
00:51:20valid for only 48 hours if the customer can't verify the email within this 48 hours then the link will be expired
00:51:28automatically and then the customer should have to be reach out to the v shopify platform for the help desk to
00:51:34login then the help desk people will again send one more verification email link okay then the customer
00:51:40should have to be verified the email by clicking on the verification link as soon as the customer
00:51:45gets verified a text message will be sent to the customer
00:51:51customers registered mobile customer registered mobile number
00:51:58with some code and the verify code page should be displayed
00:52:05upon entering the valid otp in the verify code page then the code will be verified and then the user account will be enabled
00:52:12but you know the the customers gets verified through the otp this is not required
00:52:18because however the customer should have to be verifying his mobile number when he is doing the payment
00:52:26so if we handle it at the payment side then we need to handle it here
00:52:31if we if we take the default mobile number verified mobile number at the payment stage then we have to ask this
00:52:38you are getting my point right this is not required here if the mobile number to be verified at the payment
00:52:44side because there is no guarantee that the registered mobile number should have to be used to do the
00:52:50payments no you can use any mobile number so obviously we are verifying the mobile number there
00:52:55but here we are verifying the two factor second identity so definitely this feature is up to the product
00:53:03standards maybe some people may have or maybe some people not interested to have because the customer
00:53:09execution customer onboarding process should be as simple as such it should be very smooth the customer
00:53:16should not get like the application is too complicated to onboard so to eliminate these extra things and all
00:53:23maybe someone will use the self registration link and then directly login page right but we will verify the
00:53:30customer mobile number as well so upon entering the valid otp in the verify code page then the code will
00:53:36be verified and then the customer account will get unlocked so customer account will be enabled so and
00:53:44a reset password page will be displayed to the here reset password page will be displayed to the
00:53:53change the display to set the not change the set set the credentials so to set the
00:53:59credentials he has to choose the password okay so there should be a skip option no there won't be a skip option
00:54:08customers can't skip this okay the disabled user should not be logged in that is true once users get verified
00:54:14then the the disabled customers should not log into the application once users that means once customers get
00:54:24verified then the customers can be then the customers can be logged into the vsharpify vsharpify not platform
00:54:35login to the vsharpify app vsharpify app right with their respective credentials so as soon as the customer will
00:54:47be logged in the customer dashboard can be seen like this as soon as the customers will be logged in they can
00:54:55see the dashboard as shown below so let me log in with the credentials that already i have
00:55:05maybe i have these credentials yes so this is the login page that the customers can
00:55:15log in so here we have a lot of functionality like refunds tracking and all so you can see the
00:55:24logged in user here first name and then last name and then orders can be seen here
00:55:31and then the payments and then shipping delivery this need to be
00:55:35little of course in our new design a new application we're going to modify this that so
00:55:41this is what the dashboard they can see so that's all from the customer point of view and then the
00:55:51user management point of view so let us understand the authentication use case tomorrow
00:56:00authentication again authentication will come up with the authentication
00:56:05here not authentication in this process in this this is what the user registration process right
00:56:12so user registration process for back office users and then the user registration process for the
00:56:18customers so both we have seen tomorrow before see the login part and all what we'll do is let's see the
00:56:27forget password flow let's see the forget password flow and then we will see the change password flow
00:56:37forget password flow change password flow so these two flows are pending so let us see these two flows
00:56:44tomorrow forget password flow and then because in the current system we don't have the forget password flow
00:56:51and then the change password flow is there but forget password flow is not there so we have to embed this
00:56:56forget password flow and then the change password flow so we will see this tomorrow and once this is done
00:57:04then let us start the developing this user management microservice okay um yeah that's all um
00:57:15yeah that's all from my side for today any questions i believe this is clear for all of you
00:57:20any questions will you share this document ah these documents will be shared to you once you enrolled
00:57:31for dispatch okay okay yeah yeah once the enrollment process completed then i will give the classroom
00:57:39access where you can access the microservices documents and the react integration documents these use cases
00:57:46documents project documents and all so all the documents necessary documents you can you can access
00:57:52yeah yeah yeah can we start 8 30 instead of 8 15 that's okay for me if if all the guys are okay then
00:58:02that's okay i i'll do one thing let us discuss this uh point uh arjun once after the enrollment has been
00:58:09completed because enrollment is once completed now maybe 15 minutes people make it adjust or let us see
00:58:16based on that you know 8 15 is a standard time now even i thought to move it to 8 a.m but someone
00:58:21yesterday asked me don't move to 8 a.m so that is okay because i thought everyone is now moving to offices
00:58:27probably they will minimum they will start by the 9 30 so if it's completed by the 9 15 maybe they'll get 15
00:58:33minutes of time to ready to the office that is what i thought but that's okay we'll discuss if all the members are okay
00:58:39then i don't have any issues to start at 8 30 got it fine yeah yeah okay great thanks folks thanks a lot
00:58:51um i hope i have answered all your questions alok i think i have answered your questions right
00:58:57um yeah rithi rithi and then sherath uh so great great folks see you tomorrow with the forget password
00:59:06flow and then the uh you know reset i mean change password flow and tomorrow i will showcase you
00:59:13the im wso2im and how we can achieve all these flows using the wso2im uh i'll showcase and uh what kind
00:59:22of coding we have to do to achieve this you know with with all these things i'll showcase so our system
00:59:29should have two logins one is the ss4 login second one is the database login local login and then ss4 login
00:59:34two logins our system will have right now the existing system is having only one log right but
00:59:40our upcoming system should have to be have the two log so one is the local login second one is the ss4
00:59:47meaning facebook it is also have now actually so you can see here the users will get logged in now
00:59:54with the facebook and all uh probably not here i think this is yep continue with google continue with
01:00:02facebook and all yes this is called as federated authentication single sign on authentications
01:00:08so for this one we have to use the im server so let us use the wso2im server however i'll explain
01:00:15what is the next step and all thanks a lot yeah difference between what authentication and this single
01:00:21sign answer okay single sign on in the sense once we log into one applications we should be able to log
01:00:30into other applications as well so this single sign and can be achieved in two ways one is the one is
01:00:36the using the saml document second one is using the jwt token so when the concept is jwt token this jwt
01:00:45token will use the open authorization standards that means oarth2 standards okay in oarth2 standards
01:00:51we may have the different different scopes like scope is the email scope is open id scope is uh whatever so
01:00:58different different scopes different different grant types based on that the token will be generated and
01:01:04then token have the permissions but in a nutshell as the answer for your question single sign on can be
01:01:10performed using the saml and using the jwt tokens so the difference is single sign on will enables the
01:01:21login to a one application and then no need to log into many other applications for example we can see the
01:01:27student management systems so once they log into their portal again when they go to see the you know
01:01:35exam portal you should not ask the credentials when they go and then see the you know marks portal you
01:01:40should not ask the credentials that is what the single sign on the single sign can be achieved using
01:01:45the token as well so single sign on whether we go with it or not is our application configuration
01:01:50okay so what are the other im servers there were a lot of other im servers in the market which are
01:02:02open source and which are commercial we'll discuss about this topic when we're gonna set up our w
01:02:08scope because there i will give the introduction about the im idp what is idp what is iam difference
01:02:16between idp and then im idp is available in the market open source commercial im available in the
01:02:22market open source commercial and we are going with the im not idp you may have heard about the key
01:02:28clock right key clock is just an idp it's not im im is super set of the idp idp will have only
01:02:38minimal features but yes i agree it will be very good for the small scale applications
01:02:44and it may not have all the features like how the im is providing right so that is the deal there are
01:02:50a lot of differences it's a different discussion we'll do it now when the time comes so what is
01:02:55ssl certificate and then saml a uh uh kedar shahu i think this is not the right time to discuss about
01:03:01the ssl certificate and then saml uh we're gonna set up the uh wso2 im server with the certificate with
01:03:08the ssl certificate there i'll explain what is tls what is tls what is ssl and uh you know how to
01:03:18configure the ssl meaning how to configure the tls channel what is the current version how the
01:03:23application will be protected what are the attributes in the certificate uh how the certificate can be
01:03:28renewed so all these uh things we'll discuss there i think this is very early time to discuss those
01:03:35concepts okay when time comes we'll discuss right okay guys thanks a lot and thank you so much for
01:03:42your participation and thank you so much for giving me the opportunity you know to showcase my content
01:03:48to you thanks a lot hi uh which api gateway will use you know we'll design we'll design our own api
01:03:56gateway yeah spring cloud api gateway we'll use oh yeah yeah okay thanks a lot thanks a lot folks if you guys
01:04:04are you know feel it will be helpful for you then probably you can go and then start your enrollment
01:04:09process because from the monday onwards the link will be you know discarded and then we will be come
01:04:14up with the new link that link will be available to only registered candidates so monday onwards the
01:04:19implementation will be started so mean the time if you feel like you know it will be beneficial for you
01:04:25then you can go and then start your enrollment process thanks a lot and then see you tomorrow at the same time
01:04:30thank you
1:04:31
|
Up next
1:05:27
Recommended
58:38
1:02:30
1:02:58
42:07
57:14
59:09
58:55
0:46
2:11
2:55
11:13
1:00
2:50
Be the first to comment