-
- All Known Subinterfaces:
- ServerAuthContext, ServerAuthModule
public interface ServerAuth
An implementation of this interface is used to validate received service request messages, and to secure service response messages.- See Also:
MessageInfo
,Subject
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method and Description void
cleanSubject(MessageInfo messageInfo, Subject subject)
Remove method specific principals and credentials from the subject.AuthStatus
secureResponse(MessageInfo messageInfo, Subject serviceSubject)
Secure a service response before sending it to the client.AuthStatus
validateRequest(MessageInfo messageInfo, Subject clientSubject, Subject serviceSubject)
Authenticate a received service request.
-
-
-
Method Detail
-
validateRequest
AuthStatus validateRequest(MessageInfo messageInfo, Subject clientSubject, Subject serviceSubject) throws AuthException
Authenticate a received service request. This method is called to transform the mechanism-specific request message acquired by calling getRequestMessage (on messageInfo) into the validated application message to be returned to the message processing runtime. If the received message is a (mechanism-specific) meta-message, the method implementation must attempt to transform the meta-message into a corresponding mechanism-specific response message, or to the validated application request message. The runtime will bind a validated application message into the the corresponding service invocation.This method conveys the outcome of its message processing either by returning an AuthStatus value or by throwing an AuthException.
- Parameters:
messageInfo
- A contextual object that encapsulates the client request and server response objects, and that may be used to save state across a sequence of calls made to the methods of this interface for the purpose of completing a secure message exchange.clientSubject
- A Subject that represents the source of the service request. It is used by the method implementation to store Principals and credentials validated in the request.serviceSubject
- A Subject that represents the recipient of the service request, or null. It may be used by the method implementation as the source of Principals or credentials to be used to validate the request. If the Subject is not null, the method implementation may add additional Principals or credentials (pertaining to the recipient of the service request) to the Subject.- Returns:
- An AuthStatus object representing the completion status of
the processing performed by the method.
The AuthStatus values that may be returned by this method
are defined as follows:
- AuthStatus.SUCCESS when the application request message was successfully validated. The validated request message is available by calling getRequestMessage on messageInfo.
- AuthStatus.SEND_SUCCESS to indicate that validation/processing of the request message successfully produced the secured application response message (in messageInfo). The secured response message is available by calling getResponseMessage on messageInfo.
- AuthStatus.SEND_CONTINUE to indicate that message validation is incomplete, and that a preliminary response was returned as the response message in messageInfo. When this status value is returned to challenge an application request message, the challenged request must be saved by the authentication module such that it can be recovered when the module's validateRequest message is called to process the request returned for the challenge.
- AuthStatus.SEND_FAILURE to indicate that message validation failed and that an appropriate failure response message is available by calling getResponseMessage on messageInfo.
- Throws:
AuthException
- When the message processing failed without establishing a failure response message (in messageInfo).
-
secureResponse
AuthStatus secureResponse(MessageInfo messageInfo, Subject serviceSubject) throws AuthException
Secure a service response before sending it to the client. This method is called to transform the response message acquired by calling getResponseMessage (on messageInfo) into the mechanism-specific form to be sent by the runtime.This method conveys the outcome of its message processing either by returning an AuthStatus value or by throwing an AuthException.
- Parameters:
messageInfo
- A contextual object that encapsulates the client request and server response objects, and that may be used to save state across a sequence of calls made to the methods of this interface for the purpose of completing a secure message exchange.serviceSubject
- A Subject that represents the source of the service response, or null. It may be used by the method implementation to retrieve Principals and credentials necessary to secure the response. If the Subject is not null, the method implementation may add additional Principals or credentials (pertaining to the source of the service response) to the Subject.- Returns:
- An AuthStatus object representing the completion status of
the processing performed by the method.
The AuthStatus values that may be returned by this method
are defined as follows:
- AuthStatus.SEND_SUCCESS when the application response message was successfully secured. The secured response message may be obtained by calling getResponseMessage on messageInfo.
- AuthStatus.SEND_CONTINUE to indicate that the application response message (within messageInfo) was replaced with a security message that should elicit a security-specific response (in the form of a request) from the peer. This status value serves to inform the calling runtime that (to successfully complete the message exchange) it will need to be capable of continuing the message dialog by processing at least one additional request/response exchange (after having sent the response message returned in messageInfo). When this status value is returned, the application response must be saved by the authentication module such that it can be recovered when the module's validateRequest message is called to process the elicited response.
- AuthStatus.SEND_FAILURE to indicate that a failure occurred while securing the response message and that an appropriate failure response message is available by calling getResponseMeessage on messageInfo.
- Throws:
AuthException
- When the message processing failed without establishing a failure response message (in messageInfo).
-
cleanSubject
void cleanSubject(MessageInfo messageInfo, Subject subject) throws AuthException
Remove method specific principals and credentials from the subject.- Parameters:
messageInfo
- a contextual object that encapsulates the client request and server response objects, and that may be used to save state across a sequence of calls made to the methods of this interface for the purpose of completing a secure message exchange.subject
- the Subject instance from which the Principals and credentials are to be removed.- Throws:
AuthException
- If an error occurs during the Subject processing.
-
-
Nederlandse vertaling
U hebt gevraagd om deze site in het Nederlands te bezoeken. Voor nu wordt alleen de interface vertaald, maar nog niet alle inhoud.Als je me wilt helpen met vertalingen, is je bijdrage welkom. Het enige dat u hoeft te doen, is u op de site registreren en mij een bericht sturen waarin u wordt gevraagd om u toe te voegen aan de groep vertalers, zodat u de gewenste pagina's kunt vertalen. Een link onderaan elke vertaalde pagina geeft aan dat u de vertaler bent en heeft een link naar uw profiel.
Bij voorbaat dank.
Document heeft de 11/06/2005 gemaakt, de laatste keer de 18/08/2025 gewijzigd
Bron van het afgedrukte document:https://www.gaudry.be/nl/java-api-javaee-rf-javax/security/auth/message/ServerAuth.html
De infobrol is een persoonlijke site waarvan de inhoud uitsluitend mijn verantwoordelijkheid is. De tekst is beschikbaar onder CreativeCommons-licentie (BY-NC-SA). Meer info op de gebruiksvoorwaarden en de auteur.
Referenties
Deze verwijzingen en links verwijzen naar documenten die geraadpleegd zijn tijdens het schrijven van deze pagina, of die aanvullende informatie kunnen geven, maar de auteurs van deze bronnen kunnen niet verantwoordelijk worden gehouden voor de inhoud van deze pagina.
De auteur van deze site is als enige verantwoordelijk voor de manier waarop de verschillende concepten, en de vrijheden die met de referentiewerken worden genomen, hier worden gepresenteerd. Vergeet niet dat u meerdere broninformatie moet doorgeven om het risico op fouten te verkleinen.