The Identity Registry is a core part of the infrastructure that supports the Identity Registration service. There are currently three Identity Registry environments: development, evaluation, and production. Each environment consists of one or more application servers and one or more database servers. Customer access to the Identity Registry is provided via APIs hosted on the application servers. No direct database access is permitted.

Development

• https://mango-dev.u.washington.edu:646
• Not designed for high availability.
• Not designed for geographic redundancy.
• Database usually updated nightly with a copy from production.
• Access restricted to authorized clients from UW networks.
• There is no customer Service Level Agreement (SLA).
• Generally reserved for IAM development team only.
• Changes are made freely without any customer notifications.

Evaluation

• https://mango-eval.u.washington.edu:646
• Not designed for high availability.
• Not designed for geographic redundancy.
• Database updated weekly with a copy from production on Sunday mornings.
• Access restricted to authorized clients from UW networks.
• Available for customer application testing and evaluation of new Identity Registry releases.
• Limited customer SLA, but usually available 24 hours a day, 7 days a week, other than for planned downtime.
• Unplanned downtime is not considered to be an incident since this is not a production system.
• When downtime is necessary, it is usually scheduled for Wednesday mornings between 10:00 AM and 12:00 PM.
• We usually send notices about upgrades and maintenance to eval customers at least a few days in advance.

Production

• https://mango.u.washington.edu:646
• Designed for high availability.
• Designed for geographic redundancy. Comprehensive GR exercises are conducted annually.
• Access restricted to authorized clients from UW networks.
• Service is available 24 hours a day, 7 days a week.
• Incidents are addressed based on urgency, impact, and resource availability.
• The service design supports upgrades and maintenance with no planned downtime in most cases.
• Software releases and maintenance jobs are usually scheduled for Wednesday mornings between 10:00 AM and 12:00 PM.
• We usually send notices about upgrades and maintenance to prod customers a week in advance.