Share via

3.1.5.3 User

  • Article

The User resource exposes topology information of a user’s home server. The client MUST discover the User URL by parsing the href of the Link element in the GET response from the Root resource.

If the request to the User resource does not contain a valid X-Ms-WebTicket header as specified in section 2.2.2.2, the server MUST respond with a 401 Unauthorized response.

If a valid X-Ms-WebTicket header is provided and the user’s home server information is unknown, the server MUST respond with a 404 Not Found response code and an empty body.

If a valid X-Ms-WebTicket header is provided and the user’s home server information exists on a separate server, the server MUST respond with a 200 OK response code and a User element. The User element MUST contain only one Link element with a "Redirect" Token. Semantics of the "Redirect" Token are defined in section 2.2.5.5.

If a valid X-Ms-WebTicket header is provided and the user’s home server information exists on the current server, the server MUST respond with a 200 response code and a User element in the body. The User element MAY contain any of the following links depending on what is configured in the topology.

  1. Internal/Autodiscover

  2. External/Autodiscover

  3. Internal/AuthBroker

  4. External/AuthBroker

  5. Internal/Ucwa

  6. External/Ucwa

The SipAccess types might also be present in the response depending on what is configured in the topology.