SaslServer (Java Platform SE 8 ) (original) (raw)

public interface SaslServer
Performs SASL authentication as a server.
A server such 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 according to the SASL mechanism implemented by the SaslServer. 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. It first gets an instance of a SaslServer for the SASL mechanism requested by the client:

SaslServer ss = Sasl.createSaslServer(mechanism,
"ldap", myFQDN, props, callbackHandler);
It can then proceed to use the server for authentication. For example, suppose the LDAP server received an LDAP BIND request containing the name of the SASL mechanism and an (optional) initial response. It then might use the server as follows:

 
while (!ss.isComplete()) {  
    try {  
        byte[] challenge = ss.evaluateResponse(response);  
        if (ss.isComplete()) {  
            status = ldap.sendBindResponse(mechanism, challenge, SUCCESS);  
        } else {  
            status = ldap.sendBindResponse(mechanism, challenge,  
                  SASL_BIND_IN_PROGRESS);  
            response = ldap.readBindRequest();  
        }  
    } catch (SaslException e) {  
         status = ldap.sendErrorResponse(e);  
         break;  
    }  
}  
if (ss.isComplete() && status == SUCCESS) {  
   String qop = (String) sc.getNegotiatedProperty(Sasl.QOP);  
   if (qop != null  
       && (qop.equalsIgnoreCase("auth-int")  
           || qop.equalsIgnoreCase("auth-conf"))) {  
 
     // Use SaslServer.wrap() and SaslServer.unwrap() for future  
     // communication with client  
     ldap.in = new SecureInputStream(ss, ldap.in);  
     ldap.out = new SecureOutputStream(ss, ldap.out);  
   }  
}  
 

Since:
1.5
See Also:
Sasl, SaslServerFactory

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, 2025, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.