Unique Features of K2
Integration with Legacy
Inter-working between CORBA and EJB components

The current security implementation of K2 is based on SSL inclusive client and server authentication (see Figure). A client that wants to gain access to the server must authenticate itself using an ID that is signed by a Certificate. The K2daemon and the associated server process must trust that certificate. Usually this certificate is a K2 certificate but it is possible to configure multiple trusted certificates within the server.


In the same way the client might request server authentication, in which case the client can deny of working with a server whose certificate is not authentic.

This security implementation is a coarse grained model that either grants or denies access to the server. There are no fine grained security policies.

Copyright 2008 iCMG. All rights reserved.
Site Index | Contact Us | Legal & Privacy Policy