Messages Transport The HTTPS protocol MUST be used as the transport. Common Data Types HTTP Headers The messages exchanged in the OAuth 2.0 Protocol Extensions for Broker Clients use the following HTTP headers in addition to the existing set of standard HTTP headers. Header Description This optional header can be used by the client to specify a primary refresh token when contacting the authorization endpoint. This optional header can be used by the client to prove the identity of the device from which the request is sent when contacting the authorization endpoint. x-ms-RefreshTokenCredential The x-ms-RefreshTokenCredential HTTP header is optional and can be specified by the client role of the OAuth 2.0 Protocol Extensions for Broker Clients. This header is used to pass a previously obtained primary refresh token to the authorization endpoint of the . The primary refresh token can be used by the server to authenticate the user and the device on which the client runs when processing the authorization request. The value of the x-ms-RefreshTokenCredential HTTP header MUST be a signed . The signed JWT format is defined in . The format for the x-ms-RefreshTokenCredential header is as follows. String = *(%x20-7E)
Messages Transport The HTTPS protocol MUST be used as the transport. Common Data Types HTTP Headers The messages exchanged in the OAuth 2.0 Protocol Extensions for Broker Clients use the following HTTP headers in addition to the existing set of standard HTTP headers. Header Description This optional header can be used by the client to specify a primary refresh token when contacting the authorization endpoint. This optional header can be used by the client to prove the identity of the device from which the request is sent when contacting the authorization endpoint. x-ms-RefreshTokenCredential The x-ms-RefreshTokenCredential HTTP header is optional and can be specified by the client role of the OAuth 2.0 Protocol Extensions for Broker Clients. This header is used to pass a previously obtained primary refresh token to the authorization endpoint of the . The primary refresh token can be used by the server to authenticate the user and the device on which the client runs when processing the authorization request. The value of the x-ms-RefreshTokenCredential HTTP header MUST be a signed . The signed JWT format is defined in . The format for the x-ms-RefreshTokenCredential header is as follows. String = *(%x20-7E)
%5BMS-OAPXBC%5D-170601.docx