For Campus Connect customers, NameCoach recording can be integrated with external systems in a few different ways. The effort involved is typically split between an organization's development team(s) and their IT teams. Depending on the strategy chosen, the work may fall more on one group than the other. This article will discuss three strategies and give some high level details and pointers to some resources for further consideration.
- Add the NameCoach widget script to your page (one-line change).
A screencast that walks through what the widget looks like and how you control it is here:
This screencast also walks through the implementation process at a code level.
Access to all of the NameCoach application, including the widget, is via SSL. The POST back to the NameCoach app server is also SSL encrypted. POST requests must also contain a shared secret that you configure via the Name Coach Admin UI or they'll be ignored / discarded.
In this example, I'm sending over first and last name as well as email. NAME_PAGE_CODE and AUTH_TOKEN can be found in the NameCoach Web app for the customer account holder.
NameCoach support SSO integration to its recording UI via CAS and SAML. For CAS support, your IT / IdP provider will have to contact NameCoach support to get going. For SAML (Shib), NameCoach is an Incommon member - our metadata expectations can be found here:
(Scroll down until you see NameCoach, Inc. Note that we actually run a couple SP environments, one for production and one for testing.).
When doing an SSO integration, the nice thing about the process is that accessing the recording UI is very straightforward. You link to:
Where IDP_PROVIDER is the name of an IdP provider (typically this will be your reverse FQDN with a protocol specifier) and NAME_PAGE_IDENTIFIER can be found in the Name Page admin UI for the Name Page in which you want to store the recordings. When users click on this link, if they're already authenticated in your environment, they arrive at the recording page, if they're not, they are routed back your your IdP for authentication and then redirected back to the NameCoach Web site once authentication has succeeded. As of this writing, a small amount of development work is typically required on the NameCoach side of things to handle different parameter passing schemes that may be used by your institution. Configuring the Identity Provider (IdP) to work with our implementation is something that you will have to handle. This is usually not hard to do, but can be time consuming from a project management perspective.