I’ve spent most of the last few years working on security architectures for REST-ful Web Services, using technologies like JAX-RS or Spring MVC. However, just recently I’ve had a need to go Back to the Future…I’ve been asked to run some POC experiments with J2EE container-based security. It’s been both a trip down memory lane, and an opportunity to see some exiting new technologies in action.
For those of you who may not remember the good old days of building EJBs, the basic idea is to architect an application in a classic three-tier deployment model, where the middle or business tier is a collection of Enterprise Java Beans hosted in a J2EE container. In principal, the business application developer has an easier time of it, since she can delegate all the non-functional overhead of managing transactions, and security, and persistence, etc. to the container….and just focus on coding the business logic.
While there’s still a lot not to like about developing EJBs, they have in fact come along way since I first worked with the technology, way back in 2000. Remember coding ejbCreate(), ejbActivate(), ejbPassivate(), and ejbRemove(), all by hand? Well, EJB 3.0 makes things a whole lot easier. Really. Instead of bending code for Mandatory-To-Implement (MTI) interfaces, you can just put the annotation @Stateful or @Stateless on your Java class, and you’re done.
Of course a modern specification like J2EE6 is only really useful when there is an actual container that implements that standard, so it wasn’t long before I needed to choose an actual J2EE server with which to run my tests. I know a lot of teams who use JBoss successfully, and of course many enterprises use IBM WAS, or Oracle, but I was curious to check out the latest release of Apache Geronimo. In short, I have been favorably impressed with the 3.0 release of Geronimo. I found it to be relatively easy to work with, in spite of the limited documentation. And, after all, it’s open source, so when you are wrestling with a particularly vexing configuration problem, you can just read the source code to see what it is really doing 🙂
Finally, any full application security architecture solution requires that we have a way to manage users, groups, and their corresponding roles, or permissions. The usual technology of choice for this aspect is Microsoft Active Directory or OpenLDAP. While searching for an OpenLDAP download for my test environment platform, I happened across IAM Fortress, which is a very cool implementation of ANSI RBAC, built on an OpenLDAP core. I’ve only just begun to scratch the surface of IAM Fortress, but I’ve been impressed by what I’ve seen so far, and I look forward to blogging more about this little gem in a future post.
So, for anyone who wants to continue this journey down memory lane, and at the same time explore some of the latest in new technology — J2EE, done 2013-style — I’ve posted the source code for this POC to my GitHub repository.
Enjoy! And feel free to issue a pull request 😉