​IAM / Projects / UAF_Parking

Service: UAF Parking
Vendor: T2Systems
Sponsor: UAF Parking Office
Service Platform: unknown; hosted at UAF
Authentication: currently AuthServ; planning migration to CAS
Authorization/attributes: unknown
Provisioning: unknown

Log:

2011-07-28 10:00: left voicemail for T2systems Customer Service 1-800-434-1502 (no customer service agent available); received a voicemail message back within an hour, and returned phone call to direct number provided: Joan Kimbley 317 524 7488 or 8000 434 1502 x7488

2011-07-28 11:00 - phoned direct number but could only leave voicemail; left another message including my cell number as well as desk number

2011-07-28 11:40 - return call from Joan; verified my contact data; Sean is account manager who prepared quote; case opened in T2System - will escalate to tech support. She noted that Pete Scott's status is "Away" so may be on leave.

2011-07-28/29: voicemail from Sean; returned call leaving my contact no's.

2011-08-01: Discussion with Kristen, T2Systems First line support person 317 524 3034 2011-08-01 She took names Jane Smith @ UA and Phil Scott @ T2; I referenced the quote Q-00558.

I asked for clarification on the scope of work to be done per that quote, and description of the current configuration, and technical contact to discuss implementing CAS.

On Fri, 22 Jul 2011, at 13:53 , David Bantz wrote:

Hello Pete Scott,

Jane Smith, your primary point of contact at Parking Services, University of Alaska Fairbanks (UAF), has referred me to you for technical details concerning the integration of UAF's parking application from T2 with University of Alaska's central authentication - that is, enabling people to log in to this application with their standard UAF credentials.

For some time the application has been configured to use our in-house developed authentication protocol "AuthServ?." While this has worked well for several year, UAF has deprecated this in-house protocol in favor of industry standard central authentication protocols and products, namely SAML and Shibboleth. Migration to these standards-based tools will enable us to better support integration, provide even better protection for users credentials, and improve the user experience for users because the same interface and protocol is used for many services.

My understanding is that the Quotation Q-00558 is intended to cover the cost of conversion from AuthServ? to SAML authentication. In any case, I would like to discuss both the current configuration for authenticating users and the requirements for transitioning to use of SAML and Shibboleth.

If this message should be re-directed to someone else, I will appreciate you forwarding this request and replying to tell me who I need to work with.

Thank you,

David Bantz <db@…> iam.alaska.edu Chief Information Architect; Manager, Identity & Access Management Services University of Alaska Office of Information Technology ✉ 103 Butrovich, 910 Yukon Dr, Fairbanks, AK 99775-5320 ✆ +1 907 450 8314 (o) +1 907 460 6321 (m)