IAM in Service Catalog
For overview, etc see Identity Registration Web Service REST API V2. This information is unchanged for IRWS v3.
For the IRWS v3 Swagger specification see .. link
The IRWS V2 documentation is not exhaustive. Please contact email@example.com if you have questions about V2 usage.
This guide describes the Identity Registration Web Service (IRWS) API V2. Documentation for IRWS V1 is also available . IRWS can be used to to register an identity with the Identity Registry. IRWS offers a "RESTful" programmatic interface. It exposes Identity Registry source information as addressable resources via the uniform HTTP interface; authorized clients may retrieve (GET), create (PUT), update (POST) and delete (DELETE) representations of these resources through the REST API.
An SSL client certificate is required for access (see section Certificate Authentication below). The application that uses this service must support:
All interactions with IRWS are through the following base URLs. Customer testing is generally done in the Eval environment. The Dev environment is currently dedicated to Workday integration development and testing. It is only available to Workday integration partners.
Environment URL Development https://mango-dev.u.washington.edu:646/registry/v2 Evaluation https://mango-eval.u.washington.edu:646/registry/v2 Production https://mango.u.washington.edu:646/registry/v2
Due to the sensitive nature of the information in IRWS, there are several layers of access control. The requirements for access are generally more stringent than for other services on campus.
To access IRWS you need:
These are available from UW Network Operations by emailing firstname.lastname@example.org. See Information on DNS Names and Information on Static IP Addresses . Generally, you can request both in the same email to Network Operations. Make sure to request that your UW NetID be associated with the DNS name so you can request certificates for it, and that the IP address reverse resolve to the DNS name. See the example request below.
Authentication is by certificates issued from the UW Services CA, and by hostname (DNS name) or IP address. The IP address of the client is verified in addition to the certificate. Connections will automatically be allowed if the IP address of the client reverse resolves to the subject name of the certificate presented. For special cases, you can request additional hostnames or IP addresses be allowed to authenticate with the certificate (if a hostname is specified, the IP address of the client must reverse resolve to the hostname given).
To request access to IRWS you must open a support request in UW Connect. Please send an email to email@example.com. Try to be specific about what application you are working on, what you are trying to do, and what resources you need access to. To speed up routing, you can include "Please route to the Identity and Access Management team" in your request. Your certificate may not be authorized for all of the functions described in this documentation.
IRWS supports a set of standard and custom HTTP headers that can be used by a client to express options. All the listed request headers are optional and all can be combined.
Accept: [content type1,content type2, ...]
Act-As: application name
Attribute-List: [attribute1 attribute2 attribute3 ...]
Option-List: [imprecise pretend pretty reflect]
imprecise- Overrides default PUT behavior to behave like a POST if the record already exists. This is the default behavior for some resources.
pretend- Reports what would happen if the request was carried out, but the changes are not committed. Useful for testing.
pretty- By default, IRWS returns a payload as a single line of text. For human readability you can specify this option to get a pretty-printed representation of the data.
reflect- Useful for PUTs and POSTS, specifying reflect will cause IRWS to return the current state of the resource. This is the default behavior for the
Option-List: imprecise reflect
HTTP headers are the preferred way for an application to express the IRWS options it needs. For convenience, some of the options described above can be communicated via parameters in the URI. This may be useful for user interactive testing with a browser or the curl utility. All parameters are optional and different options may be combined in one URI. Definitions and availability are provided in the previous section.
Identity records are associated with a resource. A GET on the base URL will return a list of all top-level resources for which your client is authorized. Documentation is provided for the resources listed in the table below.
|Account||The Account resource allows an authorized client to create, read, update, delete, and perform other actions related to account entities.|
|Category||The Category resource allows an authorized client to...|
|Dsubscription||The Dsubscription resource allows an authorized client to...|
|Name||The Name resource allows an authorized client to read and update source-independent names associated with person entities.|
|Pdsentry||The PDS Entry resource allows an authorized client to read Person Directory data.|
|Person||The Person resource allows an authorized client to create, read, update, delete, and perform other actions related to person entities.|
|Regid||The Regid resource allows an authorized client to manipulate attributes associated with regids.|
|Social||The Social resource allows an authorized client to create, read, and update social identities.|
|Subscription||The Subscription resource allows an authorized client to...|
IRWS uses standard HTTP return codes, as well as a few special ones. Most errors will return a JSON payload with the error class containing the
200 OK (the GET, PUT, or POST was successful) Resource (JSON) 400 Invalid identifier type provided Error (JSON) 401 403 404 Identifier provided did not match any records Error (JSON) Method Not Allowed Error (JSON) 406 Content type not supported 409 412 500 Internal Server Error None Not Implemented None 503 Service Unavailable None 901 902 903 904