Home >> All >> org >> opensst

•	org.opensst.client.* (21)	•	org.opensst.exception.* (1)	•	org.opensst.protocol.* (39)
•	org.opensst.server.* (8)	•	org.opensst.util.* (9)

Package Samples:

• org.opensst.client
• org.opensst.client.ui.adc
• org.opensst.client.ui.idc
• org.opensst.client.jetty
• org.opensst.client.keystore
• org.opensst.util.log
• org.opensst.util.net
• org.opensst.util.xml
• org.opensst.util.crypto
• org.opensst.protocol
• org.opensst.protocol.old
• org.opensst.protocol.httpproxy
• org.opensst.exception
• org.opensst.server
• org.opensst.server.http
• org.opensst.server.userdb

Classes:

• Message: This class is the base message format defintion for the openSST protocol. It provides a convenient way to build message from scratch, either from an XML message either from basic building blocks. The XML construction is used when a party receives a message. The block-by-block construction is used when a party needs to send a message to the other. This class provides high-level method to access message's content This class extensively uses JDOM to build/parse the XML tree. Note that the XML tree is build only when requested. The XML parsing is done only at class instanciation time. (i.e. between ...
• Keystore: This interface defines the behavior of a client keystore. A keystore is used to store user's private keys. A user may have multiple keys stored in the keystore (one per openSST-protected application he is using). A key is identified by a name (called a profile). Actual implementation of the keystore must ensure that the key is encrypted and should foreseen mecanisms that prevent malicious user or code to tamper with the physical repository. As it it not expected to have huge keystore on the client-side, this interface is designed with the idea that the whole keystore is loaded into memory at class ...
• OpenSSTServlet: This is a servlet version of the openSST server component. The servlet receives OpenSST requests (XML documents) which contains the adress of the wanted resource. It works as follow : If needed, the it verifies the XML document is correctly signed, It decrypts the content of the XML document It parses the XML document, It forwards the call to the destination URL and collects the byte It encrypts the result It encodes the encrypted bytes into a text based format (usually Base64) Finally, it construct a XML response document and gives it back to the caller $Date: 2002/09/30 14:40:27 $
• XMLKeystore: This is an implementation of a keystore, based on a XML file. The specs of the XML format is described in the $PROJECT_HOME/docs/openSST_keystore.txt file. I choosed to implement this as a in-memory store. Meaning that once the values are read, the file is not used anymore, until the save() method is called. While in memory, the keys are stored in the encrypted mode as they were on the file. The decoding process takes part when a key is request (using the findKey method) When a key is added, it is encrypted before being stored in memory.
• KeyStoreFactory: This class allows to actually instanciate a KeyStore object. It allows some level of flexibility by making possible to replace the keystore implementation that is returned. It also provides a mean to initialize the keystore with some implementation-specific data (for example, a keystore using a physical file to store the data may need the file name, a keystore encrypting the stored key may need the name of the algo, the parameter and the key that was used to encode the keystore, etc...) $Date$
• SimpleXMLUserDB: This is a simple implementation of the USerDB interface. This implementation is based on a XML file on the disk, it reads and writes the file before / after each access. Sample of the XML being used is : sst 1234 xA43fG ... ...
• UserSession: This class represents a user's session. This class maintain all state information between Request invocation. States are stored with a simple (key, value) system. Two keys are added to a session by this class : The session creation time (SESSION_CREATION_TIME) The session last usage time (SESSION_LAST_USAGE_TIME)
• AuthenticationDataCollectorFactory: This is a factory for the authentication data collector. This class instanciate the class given by the org.opensst.client.ui.auth system parameter. When none are defined, a CommandLineADC is used. The given class name must implemeent the org.opensst.client.ui.AuthenticationDataCollector interface. $Date: 2002/09/27 08:52:38 $
• CryptoHelper: This class provides utility methods needed both by the client and the server. This class provides all crypto related method ((de)crypt, key management, signature, base64 encoding, ...) This should be the only class able to handle crypto functions. All other classes shoudl use this class. $Date: 2002/09/05 12:24:36 $
• InitialDataCollectorFactory: This is a factory for the initial data collector. This class instanciate the class given by the org.opensst.client.ui.idc system parameter. When none are defined, a CommandLineIDC is used. The given class name must implemeent the org.opensst.client.ui.InitialDataCollector interface. $Date: 2002/09/26 18:59:30 $
• Message: This class represents a generic message exchanged between an opensst client (aka local proxy) and a server. From this base class, specialized class are inherited to represents the Request and Response messages or command messages. It also provides all the needed data handling method on the message. $Date$
• OpenSSTLogger: This class defines the logger for the openSST project. The purpose of this class is to provide some convenience method to log message and exceptions. Since we wanted to extend rather to encapsulate JDK's logger, we needed to copy/paste the factory methods ( getLogger() ) from the JDK source.
• JettyHandler: The HTTP Handler for the openSST client (aka local proxy) This class is specific to Jetty. It receives all HTTP calls made to Jetty. It is used as a dispatcher : it analyzes the request and delegates the handling to the appropriate class/method. $Date: 2002/08/05 12:48:01 $
• XMLHelper: This class provides some common functionality, shared between the openSST client and server By design, this class should be the only one able to handle XML docs. All the other classes should use utility methods provided here under. $Date: 2002/06/13 19:58:04 $
• Data: This is the base class for all data part of opensst message. The data part is the one that actually carry the data. Specific data part are used for specific purpose (ex key-enrollment etc ..) For each specific data part, a subclass must be written.
• MessageElement: This is the base class for elements of opensst message. It contains common code for all message elements (note that since an opensst message can contain another opensst message, this is also the base class for Message)
• CommandLineAuthenticationDataCollector: This is an authentication data collector. This simple class uses the command line to ask for the data. It can easily be replaced by anything else (Swing, HTML, ...) $Date: 2002/09/27 08:52:38 $
• CommandLineInitialDataCollector: This is an initial data collector. This simple class uses the command line to ask for the data. It can easily be replaced by anything else (Swing, HTML, ...) $Date: 2002/09/26 18:59:30 $
• HTTPProxyData: This is the common class for all HTTP proxy-data related content. This class defines some common behavior/content of the Data part in the case of this HTTP proxy implementation of openSST.
• InitRequest: This is an Initialization Message. Tis is the first message sent by a new Proxy. It conveys data such as the initial user's credential and the user's public key. $Date$
• PublicKeyRequest: This is a key exchange message request. This message is the first one sent anfter the proxy is started. It allows the proxy to get the server's public key. $Date$
• HTMLInitialDataCollector: This class gives to the end user an HTML GUI to enter its username, otp and so on ... I choosed to make this class HTML based to make the GUI easily customizable.
• InitialDataCollector: This interface defines the behavior of the class responsible for collecting the initial data needed at initialization time. $Date: 2002/09/26 18:59:30 $
• HTTPHelper: This class provides some common functionality, shared between the openSST client and server This class handles all HTTP related communication. $Date$
• UserDB: This interface defines the behavior of the userDB on the server side. This interface is very simple and is probably only valid for this prototype.

Home | Contact Us | Privacy Policy | Terms of Service