API java : SaslServer


javax.security.sasl
Interface SaslServer


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:

  1. SaslServer ss = Sasl.createSaslServer(mechanism,
  2. "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:
  1. while (!ss.isComplete()) {
  2. try {
  3. byte[] challenge = ss.evaluateResponse(response);
  4. if (ss.isComplete()) {
  5. status = ldap.sendBindResponse(mechanism, challenge, SUCCESS);
  6. } else {
  7. status = ldap.sendBindResponse(mechanism, challenge,
  8. SASL_BIND_IN_PROGRESS);
  9. response = ldap.readBindRequest();
  10. }
  11. } catch (SaslException e) {
  12. status = ldap.sendErrorResponse(e);
  13. break;
  14. }
  15. }
  16. if (ss.isComplete() && status == SUCCESS) {
  17. String qop = (String) sc.getNegotiatedProperty(Sasl.QOP);
  18. if (qop != null
  19. && (qop.equalsIgnoreCase("auth-int")
  20. || qop.equalsIgnoreCase("auth-conf"))) {
  21.  
  22. // Use SaslServer.wrap() and SaslServer.unwrap() for future
  23. // communication with client
  24. ldap.in = new SecureInputStream(ss, ldap.in);
  25. ldap.out = new SecureOutputStream(ss, ldap.out);
  26. }
  27. }

Since:
1.5
See Also:
Sasl, SaslServerFactory

Method Summary
 void dispose()
          Disposes of any system resources or security-sensitive information the SaslServer might be using.
 byte[] evaluateResponse(byte[] response)
          Evaluates the response data and generates a challenge.
 String getAuthorizationID()
          Reports the authorization ID in effect for the client of this session.
 String getMechanismName()
          Returns the IANA-registered mechanism name of this SASL server.
 Object getNegotiatedProperty(String propName)
          Retrieves the negotiated property.
 boolean isComplete()
          Determines whether the authentication exchange has completed.
 byte[] unwrap(byte[] incoming, int offset, int len)
          Unwraps a byte array received from the client.
 byte[] wrap(byte[] outgoing, int offset, int len)
          Wraps a byte array to be sent to the client.
 

Method Detail

getMechanismName

String getMechanismName()
Returns the IANA-registered mechanism name of this SASL server. (e.g. "CRAM-MD5", "GSSAPI").

Returns:
A non-null string representing the IANA-registered mechanism name.

evaluateResponse

byte[] evaluateResponse(byte[] response)
                        throws SaslException
Evaluates the response data and generates a challenge. If a response is received from the client during the authentication process, this method is called to prepare an appropriate next challenge to submit to the client. The challenge is null if the authentication has succeeded and no more challenge data is to be sent to the client. It is non-null if the authentication must be continued by sending a challenge to the client, or if the authentication has succeeded but challenge data needs to be processed by the client. isComplete() should be called after each call to evaluateResponse(),to determine if any further response is needed from the client.

Parameters:
response - The non-null (but possibly empty) response sent by the client.
Returns:
The possibly null challenge to send to the client. It is null if the authentication has succeeded and there is no more challenge data to be sent to the client.
Throws:
SaslException - If an error occurred while processing the response or generating a challenge.

isComplete

boolean isComplete()
Determines whether the authentication exchange has completed. This method is typically called after each invocation of evaluateResponse() to determine whether the authentication has completed successfully or should be continued.

Returns:
true if the authentication exchange has completed; false otherwise.

getAuthorizationID

String getAuthorizationID()
Reports the authorization ID in effect for the client of this session. This method can only be called if isComplete() returns true.

Returns:
The authorization ID of the client.
Throws:
IllegalStateException - if this authentication session has not completed

unwrap

byte[] unwrap(byte[] incoming,
              int offset,
              int len)
              throws SaslException
Unwraps a byte array received from the client. This method can be called only after the authentication exchange has completed (i.e., when isComplete() returns true) and only if the authentication exchange has negotiated integrity and/or privacy as the quality of protection; otherwise, an IllegalStateException is thrown.

incoming is the contents of the SASL buffer as defined in RFC 2222 without the leading four octet field that represents the length. offset and len specify the portion of incoming to use.

Parameters:
incoming - A non-null byte array containing the encoded bytes from the client.
offset - The starting position at incoming of the bytes to use.
len - The number of bytes from incoming to use.
Returns:
A non-null byte array containing the decoded bytes.
Throws:
SaslException - if incoming cannot be successfully unwrapped.
IllegalStateException - if the authentication exchange has not completed, or if the negotiated quality of protection has neither integrity nor privacy

wrap

byte[] wrap(byte[] outgoing,
            int offset,
            int len)
            throws SaslException
Wraps a byte array to be sent to the client. This method can be called only after the authentication exchange has completed (i.e., when isComplete() returns true) and only if the authentication exchange has negotiated integrity and/or privacy as the quality of protection; otherwise, a SaslException is thrown.

The result of this method will make up the contents of the SASL buffer as defined in RFC 2222 without the leading four octet field that represents the length. offset and len specify the portion of outgoing to use.

Parameters:
outgoing - A non-null byte array containing the bytes to encode.
offset - The starting position at outgoing of the bytes to use.
len - The number of bytes from outgoing to use.
Returns:
A non-null byte array containing the encoded bytes.
Throws:
SaslException - if outgoing cannot be successfully wrapped.
IllegalStateException - if the authentication exchange has not completed, or if the negotiated quality of protection has neither integrity nor privacy.

getNegotiatedProperty

Object getNegotiatedProperty(String propName)
Retrieves the negotiated property. This method can be called only after the authentication exchange has completed (i.e., when isComplete() returns true); otherwise, an IllegalStateException is thrown.

Parameters:
propName - the property
Returns:
The value of the negotiated property. If null, the property was not negotiated or is not applicable to this mechanism.
Throws:
IllegalStateException - if this authentication exchange has not completed

dispose

void dispose()
             throws SaslException
Disposes of any system resources or security-sensitive information the SaslServer might be using. Invoking this method invalidates the SaslServer instance. This method is idempotent.

Throws:
SaslException - If a problem was encountered while disposing the resources.

Ces informations proviennent du site de http://java.sun.com

Remarques

Contenu

Le contenu de cette page provient du site de Sun, et est généré depuis un cache sur l'infobrol après certains traitements automatisés. La présentation peut donc différer du document original, mais le contenu aussi. Vous pouvez utiliser ce bouton pour afficher la page originale du site de Sun :

Quels sont les motivations de cette démarche?

Maintenir les pages en cache sur différents sites peut offrir plus de disponibilité.

Chaque page est indexée dans la base de donnée, ce qui permet de retrouver facilement les informations, au moyen des sommaires, du moteur de recherche interne, etc.

Des facilités sont mises en place pour que les membres de l'infobrol puissent effectuer des traductions en français des différents documents. Ceci devrait permettre aux débutants en programmation Java de consulter les API en français s'ils maîtrisent moins bien la langue de Shakespeare. Dans le cas où une traduction a été soumise, elle est disponible au moyen d'un lien en bas de page. Si la traduction a été validée, la page s'affiche par défaut en français, et un lien en bas de page permet d'atteindre la version en anglais.

Le code sur l'infobrol est automatiquement coloré selon la syntaxe, et les différents mots clés sont transformés en liens pour accéder rapidement aux informations.

Vous avez la possibilité de partager vos expériences en proposant vos propres extraits de code en utilisant le bouton "ajouter un commentaire" en bas de page. Si vous visitez simplement l'infobrol, vous avez déjà accès à cette fonction, mais si vous étes membre du brol, vous pouvez en plus utiliser des boutons supplémentaires de mise en forme, dont la coloration automatique de vos extraits de codes.

Réseaux sociaux

Vous pouvez modifier vos préférences dans votre profil pour ne plus afficher les interactions avec les réseaux sociaux sur ces pages.

 

Nuage de mots clés

7 mots clés dont 0 définis manuellement (plus d'information...).

Avertissement

Cette page ne possède pas encore de mots clés manuels, ceci est donc un exemple automatique (les niveaux de pertinence sont fictifs, mais les liens sont valables). Pour tester le nuage avec une page qui contient des mots définis manuellement, vous pouvez cliquer ici.

Vous pouvez modifier vos préférences dans votre profil pour ne plus afficher le nuage de mots clés.

 

Astuce pour imprimer les couleurs des cellules de tableaux : http://www.gaudry.be/ast-rf-450.html
Aucun commentaire pour cette page

© Ce document issu de l′infobrol est enregistré sous le certificat Cyber PrInterDeposit Digital Numbertection. Enregistrement IDDN n° 5329-2312
Document créé le 31/08/06 02:23, dernière modification le Vendredi 17 Juin 2011, 12:12
Source du document imprimé : http://www.gaudry.be/java-api-rf-javax/security/sasl/SaslServer.html Document affiché 1 fois ce mois de Juin.
St.Gaudry©07.01.02
Outils (masquer)
||
Recherche (afficher)
Recherche :

Utilisateur (masquer)
Apparence (afficher)
Stats (afficher)
15832 documents
452 astuces.
549 niouzes.
3099 definitions.
447 membres.
8115 messages.

Document genere en :
0,59 seconde

Mises à jour :
Mises à jour du site
Citation (masquer)
Notre plus grande gloire n'est point de tomber, mais de savoir nous relever chaque fois que nous tombons.

Confucius
 
l'infobrol
Nous sommes le Samedi 02 Juin 2012, 03:28, toutes les heures sont au format GMT+1.00 Heure, heure d'été (+1)