A Simpler Way to Secure a Java Application - DZone Java

A Simpler Way to Secure a Java Application - DZone Java

In this post, you'll learn how OACC's latest feature simplifies integrating your application with this powerful open-source Java security framework and removes a coupling concern at the same time.

The Old Way of Doing Things

OACC excels at maintaining complex security relationships between your application entities and at answering any authorization questions about those relationships. Prior to the rc.5 release, every call to OACC's API required identifying your application object via an associated resource id that OACC generated for you when registering the application object you wanted to secure. Consequently, you were responsible for storing the mapping between the generated resource id and your application's native identifier for that secured object.

Read full article from A Simpler Way to Secure a Java Application - DZone Java