Timers None. Initialization None. High-Layer Triggered Events None. Message Processing Events and Sequencing Rules The following resources are available to set the publishing settings to web applications. Resource Description Proxy/RelyingPartyTrusts/{Identity}/PublishedSettings Resource used to publish a particular web application through the client. The responses to all the operations can result in the following status codes. Status code Description 200 The operation has succeeded. 400 The request is not valid. 401 Unauthorized for the specified user credentials or for the client TLS certificate. 404 The object does not exist. 405 Invalid verb used in request (GET, DELETE, POST, PUT). 409 The object already exists. 500 Version is not specified where required or any other internal error. 501 Version specified (api-version) is invalid (only valid value is 1). For all operations in this section, the server requires authenticating the proxy using client TLS authentication . The server MUST validate that the certificate that is presented by the proxy during client TLS authentication can be validated by one of the values of [Server State].ProxyTrustedCertificates. If the certificate cannot be validated, the server MUST return an HTTP error code of 401. If the operation authenticates using Integrated Windows authentication , the server MUST validate that the authenticated principal is authorized to do the corresponding operation on the server. Proxy/RelyingPartyTrusts/{Identifier}/PublishedSettings POST This operation creates a new set of publishing settings on a relying party trust. The operation is transported by a HTTP POST and can be invoked through the following URIs:
Timers None. Initialization None. High-Layer Triggered Events None. Message Processing Events and Sequencing Rules The following resources are available to set the publishing settings to web applications. Resource Description Proxy/RelyingPartyTrusts/{Identity}/PublishedSettings Resource used to publish a particular web application through the client. The responses to all the operations can result in the following status codes. Status code Description 200 The operation has succeeded. 400 The request is not valid. 401 Unauthorized for the specified user credentials or for the client TLS certificate. 404 The object does not exist. 405 Invalid verb used in request (GET, DELETE, POST, PUT). 409 The object already exists. 500 Version is not specified where required or any other internal error. 501 Version specified (api-version) is invalid (only valid value is 1). For all operations in this section, the server requires authenticating the proxy using client TLS authentication . The server MUST validate that the certificate that is presented by the proxy during client TLS authentication can be validated by one of the values of [Server State].ProxyTrustedCertificates. If the certificate cannot be validated, the server MUST return an HTTP error code of 401. If the operation authenticates using Integrated Windows authentication , the server MUST validate that the authenticated principal is authorized to do the corresponding operation on the server. Proxy/RelyingPartyTrusts/{Identifier}/PublishedSettings POST This operation creates a new set of publishing settings on a relying party trust. The operation is transported by a HTTP POST and can be invoked through the following URIs:
%5BMS-ADFSPIP%5D-160714.docx