Need a secure app that requires users to log in and provide other details? Nimbleware Apps can help. Read up on our authentication service offerings.
Authentication Server
Authentication servers use web services APIs to validate a user’s email address and password credentials when they sign in. Upon successful authentication, the servers return a randomized token that is used to match a session to a specific user. After the authentication servers validate the token, they return user-specific information—such as preferences and history—that allows client interfaces to personalize the user experience.
What else must authentication servers do?
They should support multiple types of users, including administrators, end users, and clients, and they should be able to accommodate high volumes of traffic. Their software design should be completely stateless, which means that subsequent API calls can go to a different authentication server for the same user. If an individual authentication server fails, the impact should be minimal—the server will simply be removed from the load balancer.
We can set up the following authentication services for your site:
- Register a new user
- Login
- Logout
- Change your password
- Get your user details
- Update your user details
- Check token validity
Authentication Database Server
Authentication database servers hold the authentication data requested by authentication servers. NoSQL databases are ideal, because they offer high performance as well as easy scalability with the addition of more database servers to the cluster. They also support automatic failover in case of server hardware failure. We recommend Membase and Voldemort NoSQL databases to our clients.
