"Java Security Technology Exploration Path series: Java Extensible Security Architecture" 22: SASL (III): SASL programming model. MD

--Guo Jia
Email: [Email protected]
Blog: http://blog.csdn.net/allenwells
Github:https://github.com/allenwell

Installing Java SASL

SASL security providers provide implementations of the SASL mechanism, and each provider implementation may support one or more SASL mechanisms that can be registered with JCA. In J2SE 5.0, the default method automatically registers the SUNSASL provider as a JCA provider in the JAVA security properties file, which is located in the $ $JAVA _home/jreaib/securitylava.security directory:

security.provider.7=com.sun.security.sasl.Provider

The Sun Java SASL provider (SUNSASL) supports the SASL mechanism used by a variety of popular protocols, such as LDAP, IMAP, and SMTP.
This includes the following client and server authentication mechanisms:

Client mechanism

• PLAIN (RFC 2595): Supports clear text user name/password authentication.
• CRAM-MD5 (RFC 2195): Supports hashed user name/password authentication scheme.
• DIGEST-MD5 (RFC 2831): Defines how HTTP Digest authentication is used as an SASL mechanism.
• GSSAPI (RFC 2222): Use GSSAPI to obtain authentication information and support Kerloexos V5 certification.
• EXTERNAL (RFC 2222): Obtain authentication information from external channels, such as TLS or IPSec.

Server mechanism
-CRAM-MD5
-DIGEST-MD5
-GSSAPI (Kerberos v5)

"Java Security Technology Exploration Path series: Java Extensible Security Architecture" 22: SASL (III): SASL programming model. MD