Authentication exists for you to solve this problem in a safe way and unique in the HTTP protocol.
You have these options among others listed here, these are the most used and recommended:
Basic Authentication (TLS)
Basic Authentication (Basic Authentication) is the easiest to implement, because it can be implemented most of the time, with no more library... Its problem is that it is "basic", and thus has its security level lower than other protocols. You send your username and password via an Encode Base64 encryption, and use SSL to further encrypt (TLS). After that you can create a session table, generate a hash and use it in your application by saving in browser cookies.
Oauth2(I recommend):
Oauth2 also uses SSL (TLS) to encrypt password/user and other non-binding properties as a scope. It is really a protocol, complex, and used in the authorization system of Google and Facebook. I use it on a big project of mine, and I don’t recommend it to your case.
I recommend using (if you choose Oauth2) a third party service for the job: https://auth0.com
Use of third parties as Stormpath
You can use third-party services to do all the work, but it’s an extra cost, and you’re kind of tied up with the service. https://stormpath.com/
Using Authentication and Session.
– Guilherme Nascimento
But assuming there was already, for example, a functional Login screen within the APP, how would this authentication work? Because the authentication information I use is just the configuration parameters to cross-connect Omain(url, user, password, bank name). How could I perform this other authentication without the user needing to enter another login and password?
– Léo
Do you know what token is? Instead of Session you can use token
– Guilherme Nascimento
Hello, I don’t know this concept of token... I did some research here, you could give me a small example or link so I had a north?
– Léo