Google Apps Security and Compliance Services Web Services Manual de usuario descargar pdf (Pagina 28)

26 Message Security and Compliance Application Programming Interface Guide RELEASE EA version 1.5

For example, when updating the support contact for [email protected]m and

jim@hugeISP.com, the Endpoint Resolver is first called to find the right web

service for each customer:

• For msmith@jumboinc.com, the Endpoint Resolver returns the web service

URL on System 8 since this is where the jumboinc.com domain is managed.

Your application then calls the Service Management API on System 8 to

update your company’s support contact for the msmith@jumboinc.com.

• But the Service Management API on System 6 must be used for

jim@hugeISP.com since the hugeISP.com domain is managed on System 6.

Your application makes the same Service Management request but to a

different endpoint, the web service on System 6.

Validating a Domain

Another use of Endpoint Resolver is confirming valid domains for new users. For

example, applications that provision new users in a self-service portal, need to

validate the user’s domain during the provisioning session. Since the Endpoint

Resolver uses a domain to locate a web service communication endpoint, a

convenient side effect is a quick and efficient way to validate domains:

• If the Endpoint Resolver responds with an Endpoint URL, the domain already

exists requiring the new user to provide a different domain.

• If an exception is returned, your application parses the exception names and

provides the appropriate responses. See “Exception Management” on

page 20.

• In the case of the exception UnknownEmailException, the domain was not

found and the new user’s proposed domain is valid. The self-service portal

application can continue provisioning the new user.

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 69 70

Sin comentarios

Google Apps Security and Compliance Services Web Services Manual de usuario Pagina 28