Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.ietf.jgss.* (8)

Package Samples:

org.ietf.jgss

Classes:

GSSContext: This interface encapsulates the GSS-API security context and provides the security services ( wrap(byte[],int,int,org.ietf.jgss.MessageProp) 55 , unwrap(byte[],int,int,org.ietf.jgss.MessageProp) 55 , getMIC(byte[],int,int,org.ietf.jgss.MessageProp) 55 , verifyMIC(byte[],int,int,byte[],int,int,org.ietf.jgss.MessageProp) 55 ) that are available over the context. Security contexts are established between peers using locally acquired credentials. Multiple contexts may exist simultaneously between a pair of peers, using the same or different set of credentials. GSS-API functions in a manner independent ...
GSSManager: The GSSManager class is an abstract class that serves as a factory for three GSS interfaces: GSSName , GSSCredential , and GSSContext . It also provides methods for applications to determine what mechanisms are available from the GSS implementation and what nametypes these mechanisms support. An instance of the default GSSManager subclass may be obtained through the static method getInstance() 55 , but applications are free to instantiate other subclasses of GSSManager. All but one method in this class are declared abstract. This means that subclasses have to provide the complete implementation ...
GSSCredential: This interface encapsulates the GSS-API credentials for an entity. A credential contains all the necessary cryptographic information to enable the creation of a context on behalf of the entity that it represents. It may contain multiple, distinct, mechanism specific credential elements, each containing information for a specific security mechanism, but all referring to the same entity. A credential may be used to perform context initiation, acceptance, or both. GSS-API implementations must impose a local access-control policy on callers to prevent unauthorized callers from acquiring credentials ...
MessageProp: This is a utility class used within the per-message GSSContext methods to convey per-message properties. When used with the GSSContext interface's GSSContext.wrap(byte[],int,int,org.ietf.jgss.MessageProp) 55 and GSSContext.getMIC(byte[],int,int,org.ietf.jgss.MessageProp) 55 methods, an instance of this class is used to indicate the desired QOP and to request if confidentiality services are to be applied to caller supplied data (wrap only). To request default QOP, the value of 0 should be used for QOP. When used with the GSSContext.unwrap(byte[],int,int,org.ietf.jgss.MessageProp) 55 and GSSContext.verifyMIC(byte[],int,int,byte[],int,int,org.ietf.jgss.MessageProp) ...
GSSName: This interface encapsulates a single GSS-API principal entity. Different name formats and their definitions are identified with universal Object Identifiers (Oids). The format of the names can be derived based on the unique oid of its namespace type. Example Code GSSManager mgr = GSSManager.getInstance(); // create a host based service name GSSName name = mgr.createName("service@host", GSSName.NT_HOSTBASED_SERVICE); Oid krb5 = new Oid("1.2.840.113554.1.2.2"); GSSName mechName = name.canonicalize(krb5); // the above two steps are equivalent to the following GSSName mechName = mgr.createName("service@host", ...
ChannelBinding: The GSS-API accommodates the concept of caller-provided channel binding information. Channel bindings are used to strengthen the quality with which peer entity authentication is provided during context establishment. They enable the GSS-API callers to bind the establishment of the security context to relevant characteristics like addresses or to application specific data. The caller initiating the security context must determine the appropriate channel binding values to set in the GSSContext object. The acceptor must provide an identical binding in order to validate that received tokens possess ...
Oid: This class represents Universal Object Identifiers (Oids) and their associated operations. Oids are hierarchically globally-interpretable identifiers used within the GSS-API framework to identify mechanisms and name formats. The structure and encoding of Oids is defined in ISOIEC-8824 and ISOIEC-8825. For example the Oid representation of Kerberos V5 mechanism is "1.2.840.113554.1.2.2". The GSSName name class contains public static Oid objects representing the standard name types defined in GSS-API.
GSSException: This exception is thrown whenever a fatal GSS-API error occurs including mechanism specific errors. It may contain both, the major and minor, GSS-API status codes. The mechanism implementers are responsible for setting appropriate minor status codes when throwing this exception. Aside from delivering the numeric error code(s) to the caller, this class performs the mapping from their numeric values to textual representations. All Java GSS-API methods are declared throwing this exception.

Home | Contact Us | Privacy Policy | Terms of Service