1. 1 User Registration System (URS) Onboarding & Migration EED UTC February 18, 2014

2. 2 EED UTC February 18, 2014 What is URS? –URS by the numbers –Architecture Current Application Clients URS 4.0 –The Basics –Authentication Workflow –Migration Plan Talk Back This is the boring agenda slide…

3. 3 EED UTC February 18, 2014 So what is URS again (again)?

4. 4 EED UTC February 18, 2014  Identity across EOSDIS URS is about…  Uniformity  Standardization  Metrics

5. 5 EED UTC February 18, 2014  Over 100,000 users A few numbers… 99.99% uptime for last 6 months ~1.5M authentications per week Redundancy and failover

6. 6 EED UTC February 18, 2014 Logical Architecture

7. 7 EED UTC February 18, 2014 Current Application Clients ECHO LANCE Earthdata AMSR-E EMS GES DISC ASF LP DAAC …and others These existed (some in limited fashion) in 2012. GES DISC wasn’t in production in 2012.

8. 8 EED UTC February 18, 2014 URS 4.0

9. 9 EED UTC February 18, 2014

10. 10 EED UTC February 18, 2014

11. 11 EED UTC February 18, 2014 Authentication Workflow 1.User visits partner website (and a protected resource) via their web browser 2.Partner website redirects user to URS 3.User logs in via URS 4.URS sends a code to the user’s web browser…...and redirects the user back to the partner website. 5.Partner website uses the user’s code to get a token for access via URS. UserPartner Website

12. 12 EED UTC February 18, 2014 Migration

13. 13 EED UTC February 18, 2014 You’ll be getting a survey

14. 14 EED UTC February 18, 2014 You already have URS as part of your application’s workflow You already have an existing URS application ID (or two, or three…) You get a call from us to work up a specific migration plan for your applications You know you’re a 3.0 client if…

15. 15 EED UTC February 18, 2014 All your questions begin with “So when the policy says…” You’re adding up all the hours it will take to implement this new thing in your application You just want to know how to avoid getting a nasty call from Jeanne Behnke You know you’re a 4.0 client if…

16. 16 EED UTC February 18, 2014 Testing is paramount –URS is in UAT –Your application should be in a test environment, too Technology is the driver –We are writing reference implementations now –Apache (via module), Drupal, PHP We favor partial implementations (for now) –A PHP bulletin board is better than your most critical OpenDAP system –Ease of integration comes one system at a time Testing, Technology, Tartial

17. 17 EED UTC February 18, 2014 NameRoleEmailPhone Andy MitchellESDIS Andrew.e.mitchell@nasa.gov 301-614-5189 Chan YeeURS Task Lead Chan_yee@raytheon.com 301-851-8264 Brett McLaughlinTechnical Lead brett@element84.com 214-287-0976 Ken CockerillURS Advocate Kenneth.l.cockerill@nasa.gov 301-851-8439 Stanley StewartOperations Lead Stanley.s.stewart@nasa.gov 301-851-8080 Talk Back

18. 18 EED UTC February 18, 2014 Want to Play? support@earthdata.nasa.gov Brett McLaughlin brett@element84.com brett@element84.com Ken Cockerill kenneth.l.cockerill@nasa.gov