AES, DES, Blowfish with digest or salt, md5 … sometimes these terms can drive you crazy when you must encrypt your data. In this post I’d like to make a few order to help you make the right choice in the right direction.
Have you ever thought of using your voice instead of plain text string to get authenticated?
It’s not science fiction, it’s called biometric authentication and, some company as Google, are going to moving on in the next years.
In this article, I’m going to illustrate it using an open source library and a little example.
Spring Security makes available a good base customizable authentication layer to transform a plain web application into a secure one.
In this article I’ll show some of the behaviours that are customizable in a Spring solution. Obviously, I won’t describe all the possible parts but only a brief part of them but, I’m sure, once you got them, it’d be easy to understand how to customize even the deeper part of the code.
A short summer article about the asymmetric key pairs in order to guarantee an encrypted communication between two endpoints.
I’ll show the main steps to achieve this aim using jdk tool (keytool) and a short java example.
In this article I’ll show how to develop a solution that uses OAuth2 as authentication protocol with Authorization code during the flow process.
Spring Framework has been used as backbone of the solution and the user’s token generated have been persisted in a MySQL Database.
Continuing from my previous post, I’ll show the client integration to a CAS Authentication service using a little example. It will show how calling the authentication and how verify user credentials once authenticated.
Spring Security supports a lot of different authentication systems. One of that is the central authentication service (CAS) which allows the users to authenticate in a Web Application (or different Web Applications) using a unique central service.
In this article, I’ll show the integration of the CAS with Spring security framework. As usual, by using an example.