Share via

3.2.5.7 Receiving a LinkViewerToMacSecurityResponse Message

  • Article

The server MUST first follow the steps specified in section 3.2.5.1. Also, the server MUST verify that the LinkViewerToMacSecurityResponse message adheres to the syntax specified in section 2.2.4.24.

The server MUST process the credentials in the pToken field of the LinkViewerToMacSecurityResponse message using the same authentication mechanism that the server previously specified in the pToken field of the LinkMacToViewerSecurityChallenge message. If the authentication algorithm requires that a challenge be sent (for example, because the credentials in the pToken field are incorrect), the server MUST send a LinkMacToViewerSecurityChallenge message. If the pToken field of the LinkViewerToMacSecurityResponse message includes the NTLM_AUTH structure (section 2.2.4.14.1) and the LinkMacToViewerSecurityChallenge will include an NTLM challenge token (as defined in [MS-NLMP] section 2.2.1.2), then the pToken field in the LinkMacToViewerSecurityChallenge message MUST include the NTLM_AUTH structure. If the pToken field of the LinkViewerToMacSecurityResponse message does not include the NTLM_AUTH structure, then the pToken field in the LinkMacToViewerSecurityChallenge message MUST NOT include the NTLM_AUTH structure.

If the server sent a LinkMacToViewerSecurityChallenge message, the server MUST wait for a LinkViewerToMacSecurityResponse message to be received. How to process this message is specified in section 3.2.5.7.

If the server did not send a LinkMacToViewerSecurityChallenge message, the server MUST send a LinkMacToViewerReportOpenFile (section 2.2.4.7) message.

The value of the openFileId field of the LinkMacToViewerReportOpenFile message MUST be set to the value of the File-ID variable in the abstract data model.

If the server sent a LinkMacToViewerReportOpenFile message, the server MUST wait for a LinkViewerToMacReadBlock message to be received. How to process this message is specified in section 3.2.5.8.