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

Quick Search    Search Deep
Home >> All >> javax >> security

•javax.security.auth.* (41)•javax.security.cert.* (8)•javax.security.jacc.* (18)•javax.security.sasl.* (12)

Package Samples:

• javax.security.auth.callback
• javax.security.auth
• javax.security.auth.login
• javax.security.auth.spi
• javax.security.auth.x500
• javax.security.cert
• javax.security.sasl
• javax.security.jacc
• javax.security.auth.kerberos

Classes:

• SaslClient: Performs SASL authentication as a client. A protocol library such as one for LDAP gets an instance of this class in order to perform authentication defined by a specific SASL mechanism. Invoking methods on the SaslClient instance process challenges and create responses according to the SASL mechanism implemented by the SaslClient . As the authentication proceeds, the instance encapsulates the state of a SASL client's authentication exchange. Here's an example of how an LDAP library might use a SaslClient . It first gets an instance of a SaslClient: SaslClient sc = Sasl.createSaslClient(mechanisms, ...
• AuthPermission: A permission controlling access to authentication service. The actions field of auth permission objects is ignored; the whole of the permission is defined by the target . The authentication permission targets recognized are: doAs Allows access to the Subject#doAs(javax.security.auth.Subject java.security.PrivilegedAction) methods. doAsPrivileged Allows access to the Subject.doAsPrivileged(javax.security.auth.Subject, java.security.PrivilegedAction, java.security.AccessControlContext) 55 methods. getSubject Allows access to the Subject associated with a thread. getSubjectFromDomainCombiner Allows ...
• CallbackHandler: An application implements a CallbackHandler and passes it to underlying security services so that they may interact with the application to retrieve specific authentication data, such as usernames and passwords, or to display certain information, such as error and warning messages. CallbackHandler s are implemented in an application-dependent fashion. For example, implementations for an application with a graphical user interface (GUI) may pop up windows to prompt for requested information or to display error messages. An implementation may also choose to obtain requested information from an alternate ...
• SaslServer: Performs SASL authentication as a server. A server such as an LDAP server gets an instance of this class in order to perform authentication defined by a specific SASL mechanism. Invoking methods on the SaslServer instance generates challenges corresponding to the SASL mechanism implemented by the SaslServer instance. As the authentication proceeds, the instance encapsulates the state of a SASL server's authentication exchange. Here's an example of how an LDAP server might use a SaslServer instance. It first gets an instance of a SaslServer for the SASL mechanism requested by the client: SaslServer ...
• Callback: Implementations of this interface are passed to a CallbackHandler , allowing underlying security services the ability to interact with a calling application to retrieve specific authentication data such as usernames and passwords, or to display certain information, such as error and warning messages. Callback implementations do not retrieve or display the information requested by underlying security services. Callback implementations simply provide the means to pass such requests to applications, and for applications, if appropriate, to return requested information back to the underlying security ...
• SaslServerFactory: An interface for creating instances of SaslServer . A class that implements this interface must be thread-safe and handle multiple simultaneous requests. It must also have a public constructor that accepts no arguments. This interface is not normally accessed directly by a server, which will use the Sasl static methods to create a SaslServer instance instead. However, a particular environment may provide and install a new or different SaslServerFactory .
• Sasl: A static class for creating SASL clients and servers. This class defines the policy of how to locate, load, and instantiate SASL clients and servers. For example, an application or library gets a SASL client instance by doing something like: SaslClient sc = Sasl.createSaslClient(mechanisms, authorizationID, protocol, serverName, props, callbackHandler); It can then proceed to use the instance to create an authenticated connection. Similarly, a server gets a SASL server instance by using code that looks as follows: SaslServer ss = Sasl.createSaslServer(mechanism, protocol, serverName, props, ca ...
• AuthenticationException: This exception is thrown by a SASL mechanism implementation to indicate that the SASL exchange has failed due to reasons related to authentication, such as an invalid identity, passphrase, or key. Note that the lack of an AuthenticationException does not mean that the failure was not due to an authentication error. A SASL mechanism implementation might throw the more general SaslException instead of AuthenticationException if it is unable to determine the nature of the failure, or if does not want to disclose the nature of the failure, for example, due to security reasons.
• SaslClientFactory: An interface for creating instances of SaslClient . A class that implements this interface must be thread-safe and handle multiple simultaneous requests. It must also have a public constructor that accepts no arguments. This interface is not normally accessed directly by a client, which will use the Sasl static methods to create a client instance instead. However, a particular environment may provide and install a new or different SaslClientFactory .
• PolicyContextHandler: This interface defines the methods that must be implemented by handlers that are to be registered and activated by the PolicyContext class. The PolicyContext class provides methods for containers to register and activate container-specific PolicyContext handlers. Policy providers use the PolicyContext class to activate handlers to obtain (from the container) additional policy relevant context to apply in their access decisions. All handlers registered and activated via the PolicyContext class must implement the PolicyContextHandler interface.
• PrivateCredentialPermission: A permission governing access to a private credential. The action of this permission is always "read" -- meaning that the private credential information can be read from an object. The target of this permission is formatted as follows: CredentialClassName ( PrinicpalClassName PrincipalName )* CredentialClassName is either the name of a private credential class name, or a wildcard character ( '*' ). PrinicpalClassName is the class name of a principal object, and PrincipalName is a string representing the principal, or the wildcard character.
• EJBRoleRefPermission: Class for EJB isCallerInRole(String reference) permissions. An EJBRoleRefPermission is a named permission and has actions. The name of an EJBRoleRefPermission contains the value of the ejb-name element in the application's deployment descriptor that identifies the EJB in whose context the permission is being evalutated. The actions of an EJBRoleRefPermission identifies the role reference to which the permission applies. An EJBRoleRefPermission is checked to determine if the subject is a member of the role identified by the reference.
• PolicyConfigurationFactory: Abstract factory and finder class for obtaining the instance of the class that implements the PolicyConfigurationFactory of a provider. The factory will be used to instantiate PolicyConfiguration objects that will be used by the deployment tools of the container to create and manage policy contexts within the Policy Provider. Implementation classes must have a public no argument constructor that may be used to create an operational instance of the factory implementation class.
• LoginModule: The base interface for login methods in the Java Authentication and Authorization Service (JAAS). This interface is used by service providers that implement login services, and is used internally by the JAAS system. It is not useful to application programmers, who should use the javax.security.auth.login.LoginContext instead.
• LanguageCallback: Underlying security services instantiate and pass a LanguageCallback to the handle() method of a CallbackHandler to retrieve the java.util.Locale used for localizing text.
• ConfirmationCallback: Underlying security services instantiate and pass a ConfirmationCallback to the handle() method of a CallbackHandler to ask for YES/NO, OK/CANCEL, YES/NO/CANCEL or other similar confirmations.
• TextOutputCallback: Underlying security services instantiate and pass a TextOutputCallback to the handle() method of a CallbackHandler to display information messages, warning messages and error messages.
• ChoiceCallback: Underlying security services instantiate and pass a ChoiceCallback to the handle() method of a CallbackHandler to display a list of choices and to retrieve the selected choice(s).
• UnsupportedCallbackException: Signals that a CallbackHandler does not recognize a particular Callback .
• TextInputCallback: Underlying security services instantiate and pass a TextInputCallback to the handle() method of a CallbackHandler to retrieve generic text information.
• RealmChoiceCallback: This callback is used by SaslClient and SaslServer to obtain a realm given a list of realm choices.
• PasswordCallback: Underlying security services instantiate and pass a PasswordCallback to the handle() method of a CallbackHandler to retrieve password information.
• AuthorizeCallback: This callback is used by SaslServer to determine whether one entity (identified by an authenticated authentication ID) can act on behalf of another entity (identified by an authorization ID).
• NameCallback: Underlying security services instantiate and pass a NameCallback to the handle() method of a CallbackHandler to retrieve name information.
• CertificateNotYetValidException: Signals that a certificate is not yet valid. This class is deprecated in favor of the java.security.cert.CertificateNotYetValidException class. It should not be used in new applications.

Home | Contact Us | Privacy Policy | Terms of Service