1.

How Authentication Is Handled In Filenet P8?

Answer»

Authentication is a process of checking if the user entered credentials are correct. FileNet

P8 uses two different standards for authentication:

  1. Java Authentication and Authorization Service (JAAS) standard JAAS PROVIDES a policy-based framework to determine who is invoking a Java application. The Content Engine EJB resides within the J2EE Application Server's EJB container. CE therefore uses JAAS pluggable framework for authentication.
  2. Web Services SECURITY (WS-Security) standard FileNet web services uses WS-Security standards for authentication. Like JAAS, WSSecurity is an extensible standard which supports multiple security token formats i.e. Username Token, Kerberos Tokens, SSL X.509 Tokens etc.

When the Content Engine server receives a web service request, the Content Engine Web Service Listener extracts the WS-Security header and performs a JAAS login based on its CONTENTS. If this JAAS login is SUCCESSFUL, then the Web service listener passes the request onto the Content Engine EJB layer within the EJB container.

Authentication is a process of checking if the user entered credentials are correct. FileNet

P8 uses two different standards for authentication:

When the Content Engine server receives a web service request, the Content Engine Web Service Listener extracts the WS-Security header and performs a JAAS login based on its contents. If this JAAS login is successful, then the Web service listener passes the request onto the Content Engine EJB layer within the EJB container.



Discussion

No Comment Found