TOPT takes the password expiry policy to the extreme by expiring your password at an even faster rate like say every 30 seconds! The problem here is that you cannot change your password every 30 seconds so to make this work, TOTP uses an algorithm to change the password for us. This password expiry policy gets around the above mention problem every 6 months.

In most operating system you can configured a password expiry policy where users are forced to change their password at regular intervals eg. Password are typically static they do not change over time so if someone knows your password then your account is compromised. We are all familiar with the concept of password. Configure container managed security to use TOTP for login.Create the login and user registration with JSF Faces Flow.Setup JDBC realm for Glassfish application server in preparation for using it in our form based authentication.In the first part, I’ll give a brief intro to Google Authenticator/time based onetime password and how it works.The blog is broken into the following sections Hopefully the journey is as pleasant as the destination 😉

You can get a copy of the source when you reach the end of the blog. I’ll describe what I did and some of the issues I found. I installed Google Authenticator on my phone and started experimenting it with Java EE security. After reading the following blog on time-based one time password (TOTP), I wanted to see if I could add an additional layer of security into Java EE’s security.

Totp google authenticator java