- Package javax.security.sasl
- Package javax.security.sasl Description
- SASL Overview
- Usage
- Related Documentation
- Package javax.security.sasl
- SASL Overview
- Usage
- Related Documentation
- Package javax.security.sasl
- SASL Overview
- Usage
- Related Documentation
- Package javax.security.sasl
- Package javax.security.sasl Description
- SASL Overview
- Usage
- Related Documentation
Package javax.security.sasl
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).
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.
Package javax.security.sasl Description
Contains class and interfaces for supporting SASL. This package defines classes and interfaces for SASL mechanisms. It is used by developers to add authentication support for connection-based protocols that use SASL.
SASL Overview
- DIGEST-MD5 (RFC 2831). This mechanism defines how HTTP Digest Authentication can be used as a SASL mechanism.
- Anonymous (RFC 2245). This mechanism is anonymous authentication in which no credentials are necessary.
- External (RFC 2222). This mechanism obtains authentication information from an external source (such as TLS or IPsec).
- S/Key (RFC 2222). This mechanism uses the MD4 digest algorithm to exchange data based on a shared secret.
- GSSAPI (RFC 2222). This mechanism uses the GSSAPI for obtaining authentication information.
Usage
Users of this API are typically developers who produce client library implementations for connection-based protocols, such as LDAPv3 and IMAPv4, and developers who write servers (such as LDAP servers and IMAP servers). Developers who write client libraries use the SaslClient and SaslClientFactory interfaces. Developers who write servers use the SaslServer and SaslServerFactory interfaces. Among these two groups of users, each can be further divided into two groups: those who produce the SASL mechanisms and those who use the SASL mechanisms. The producers of SASL mechanisms need to provide implementations for these interfaces, while users of the SASL mechanisms use the APIs in this package to access those implementations.
Related Documentation
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2023, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.
Package javax.security.sasl
Contains class and interfaces for supporting SASL. This package defines classes and interfaces for SASL mechanisms. It is used by developers to add authentication support for connection-based protocols that use SASL.
SASL Overview
- DIGEST-MD5 (RFC 2831). This mechanism defines how HTTP Digest Authentication can be used as a SASL mechanism.
- Anonymous (RFC 2245). This mechanism is anonymous authentication in which no credentials are necessary.
- External (RFC 2222). This mechanism obtains authentication information from an external source (such as TLS or IPsec).
- S/Key (RFC 2222). This mechanism uses the MD4 digest algorithm to exchange data based on a shared secret.
- GSSAPI (RFC 2222). This mechanism uses the GSSAPI for obtaining authentication information.
Usage
Users of this API are typically developers who produce client library implementations for connection-based protocols, such as LDAPv3 and IMAPv4, and developers who write servers (such as LDAP servers and IMAP servers). Developers who write client libraries use the SaslClient and SaslClientFactory interfaces. Developers who write servers use the SaslServer and SaslServerFactory interfaces. Among these two groups of users, each can be further divided into two groups: those who produce the SASL mechanisms and those who use the SASL mechanisms. The producers of SASL mechanisms need to provide implementations for these interfaces, while users of the SASL mechanisms use the APIs in this package to access those implementations.
Related Documentation
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.
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).
Package javax.security.sasl
Contains class and interfaces for supporting SASL. This package defines classes and interfaces for SASL mechanisms. It is used by developers to add authentication support for connection-based protocols that use SASL.
SASL Overview
- DIGEST-MD5 (RFC 2831). This mechanism defines how HTTP Digest Authentication can be used as a SASL mechanism.
- Anonymous (RFC 2245). This mechanism is anonymous authentication in which no credentials are necessary.
- External (RFC 2222). This mechanism obtains authentication information from an external source (such as TLS or IPsec).
- S/Key (RFC 2222). This mechanism uses the MD4 digest algorithm to exchange data based on a shared secret.
- GSSAPI (RFC 2222). This mechanism uses the GSSAPI for obtaining authentication information.
Usage
Users of this API are typically developers who produce client library implementations for connection-based protocols, such as LDAPv3 and IMAPv4, and developers who write servers (such as LDAP servers and IMAP servers). Developers who write client libraries use the SaslClient and SaslClientFactory interfaces. Developers who write servers use the SaslServer and SaslServerFactory interfaces. Among these two groups of users, each can be further divided into two groups: those who produce the SASL mechanisms and those who use the SASL mechanisms. The producers of SASL mechanisms need to provide implementations for these interfaces, while users of the SASL mechanisms use the APIs in this package to access those implementations.
Related Documentation
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.
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).
Package javax.security.sasl
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).
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.
Package javax.security.sasl Description
Contains class and interfaces for supporting SASL. This package defines classes and interfaces for SASL mechanisms. It is used by developers to add authentication support for connection-based protocols that use SASL.
SASL Overview
- DIGEST-MD5 (RFC 2831). This mechanism defines how HTTP Digest Authentication can be used as a SASL mechanism.
- Anonymous (RFC 2245). This mechanism is anonymous authentication in which no credentials are necessary.
- External (RFC 2222). This mechanism obtains authentication information from an external source (such as TLS or IPsec).
- S/Key (RFC 2222). This mechanism uses the MD4 digest algorithm to exchange data based on a shared secret.
- GSSAPI (RFC 2222). This mechanism uses the GSSAPI for obtaining authentication information.
Usage
Users of this API are typically developers who produce client library implementations for connection-based protocols, such as LDAPv3 and IMAPv4, and developers who write servers (such as LDAP servers and IMAP servers). Developers who write client libraries use the SaslClient and SaslClientFactory interfaces. Developers who write servers use the SaslServer and SaslServerFactory interfaces. Among these two groups of users, each can be further divided into two groups: those who produce the SASL mechanisms and those who use the SASL mechanisms. The producers of SASL mechanisms need to provide implementations for these interfaces, while users of the SASL mechanisms use the APIs in this package to access those implementations.
Related Documentation
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2023, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.