JAAS

View: [ 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 ]

Articles
  

Articles:
  • Implement JAAS based Authentication and Authorization for ADF Faces applications on OC4J 10.1.3 by Lucas Jellema   - [Clicks: 103]
    In this article, we will see how to implement Authentication and Authorization for the world’s simplest ADF Faces application, that demonstrates all features - including logout, presenting the name of the logged in user and hide & display of elements depending on the role of the current user. We will deploy this simplest of applications on the Embedded OC4J 10.1.3 server in JDeveloper as well as on a Stand-alone OC4J instance. This article only discusses file based (jazn-data.xml) repositories. In a subsequent article we will see how we can use our own custom Database based mechanism for Authentication and Authorization.
    [Includes sample code]
    http://technology.amis.nl/blog/?p=1426 - Dec, 2006
  • Using JAAS in Java EE and SOA Environments by Denis Pilipchuk   - [Clicks: 45]
    Denis Pilupchuk looks at JAAS' incomplete integration with Java EE And SOA, and assesses future directions for JAAS.
    http://today.java.net/pub/a/today/2006/09/14/using-jaas-in-ee-and-soa.html - Sep, 2006
  • JAAS in the Enterprise by Raymond K. Ng, Ganesh Kirti   - [Clicks: 261]
    Since 2001 when Java Authentication and Authorization Service (JAAS) was formally included in the Java 2 Platform Enterprise Edition (J2EE) 1.3 platform specification, the J2EE community has been grappling with the issue of JAAS/J2EE integration. On the surface, JAAS seems to be an excellent complement to J2EE: JAAS defines a pluggable Application Programming Interface (API) for authentication modules and a fine-grained Subject-based authorization model, which are both lacking in the existing J2EE security model. Since JAAS is officially part of the J2EE platform specification, it's not unreasonable to expect that you can now leverage the JAAS framework to build portable enterprise applications that have advanced authentication and authorization requirements. Unfortunately, any Java architects or developers who go down this path for their applications will soon be confronted with the harsh reality: Instead of finding a landscape defined by an unified integration architecture, they'll discover a landscape littered with incompatible vendor-specific APIs and frameworks.
    http://java.sys-con.com/read/171477.htm - Jan, 2006

[Top]