No, we already made our application up and running, and that's where I'm going to access the login
page and this is the page that we can.
Let's try to make your backend application also at the AT&T port so that you web application can start
communicating with the backend application.
For that, I'm going to the East Bank, back an application by clicking on as your application.
This will start my backend application at the Port AT&T, which we are already configured in the US,
so we can see here get started on board AT&T.
Now we are going to call a Salvy convocation from Utterback.
Let's try to go to the Groser.
Want to enter the credentials like happy and great example, dot com it is the email and password is
one, two, three, four, five.
Because clicking on the signing, I just wanted to open the browser console so we can see any kind of
errors that it comes.
I'm clicking signing and you can see now we are getting an error saying that access to this and service
from Orison, which is the UI application hostname on board, has been blocked by correspondence.
So according to us, it has to work.
There is nothing wrong.
Right.
So we have a service on the backend and a user application.
Want to communicate with the back the service and it is also passing the valid connections.
If the current trends are wrong, it has two three four zero one error, but even the credentials are
also not considered and it straightaway throwing an error errors related to cosponsorship.
Let's try to see what it costs in the next room.