...
Setting Up Test Environment
The IdP Proxy and supporting components are currently operating in four environments: Continuous Integrated (CI) supporting development activities, TEST (an internal environment for development testing), PILOT (for early production stage proof of operations), and PROD (the production environment used by students and staff). In order to implement technical integration and facilitate ongoing testing, colleges must stand up a testing environment to ensure their IDP solution is able to authenticate with the Proxy and CCC applications.
The college TEST environment will access the CCC's PILOT environment for the Proxy and various applications.
Connecting to the Proxy
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Connecting to the Proxy from CCCAssess
As part of the overall identity federation project, Unicon has configured and deployed a CCC IdP Proxy through which applications available across CCC campuses can centralize authentication requests. The IdP proxy then contacts the appropriate “real’ IdP to complete requests. The goal of this design is to simplify and accelerate system wide technology adoption and provide uniform experiences for key users.
The IdP Proxy and supporting components are currently operating in three environments, Continuous Integrated (supporting development activities), Test (supporting functional testing), and Pilot (for early stage proof of operations with early adopters). It will soon be deployed to a Production environment.
In addition to the question of how Unicon will be able to support a critical cog in the CCC infrastructure on a 7x24 basis with very high, e.g. 99.999% availability, several “bigger picture” questions have been raised, primarily by Unicon’s Mike Grady. Mike is an architect in Unicon’s IAM practice with broad experience deploying IAM solutions to higher ed institutions, including federated identity.
...