Provide Mobile User Session
Sharing Through OAuth and SAML
Sascha Preibisch – Principal Software Architect – CA Technologies
DO3X50E
DEVOPS
5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
For Informational Purposes Only
Terms of this Presentation
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
6 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Abstract
Users of mobile apps like to login to an app once and not get
asked for credentials again. In the case of an enterprise that has
integrations with third-party web applications it may be difficult
to re-use the user session the native app is maintaining.
In this workshop we will show how to leverage the
CA Mobile API Gateway features to forward the user session
using OAuth and SAML.
Sascha
Preibisch
CA Technologies
Principal Software
Architect
7 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Agenda
WHAT IS THE SCENARIO
WHAT ARE THE CHALLENGES
WHAT IS CA MOBILE API GATEWAY
SWITCHING FROM NATIVE APP TO WEB APPLICATION
1
2
3
4
8 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
What Is The Scenario
Components that are involved
API
Gateway
Backend
DB
Third-Party
Web
Application
Federated Token Server
(SAML)
Native App
Browser
Internet
DMZ
IDP
Device
9 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Third-Party
Web
Application
API
Gateway
Backend
DB
Federated Token Server
(SAML)
Native App
Browser
Internet
DMZ
IDP
Device
What Are The Challenges
User session
10 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Backend
DB
Federated Token Server
(SAML)
DMZ
IDP
Device
What Is CA Mobile API Gateway
It is the component that connects it all
DMZ
Native App
Browser
Internet
CA
Mobile API
Gateway
Third-Party
Web
Application
11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Device
Switching From Native App To Web Application
From OAuth to SAML
DMZ
OAuth
Switch
Context
Validate
OAuth
session
Request
SAML
Token
WebSSO
Native App
Browser
Federated Token Server
(SAML)
Internet
CA
Mobile API
Gateway
Third-Party
Web
Application
12 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Recommended Sessions
SESSION # TITLE DATE/TIME
DO3T80S
Case Study: Centrica – How CA APIM is enabling Britain’s
largest energy provider to know their customer before they
open the door
11/16/2016 at 03:00 pm
DO3T05S
Case Study: LG&E/KU - How Mobile Apps, APIs With
Microservices and CA API Management are Helping to Shape
the Company’s Future
11/16/2016 at 03:45 pm
DO3T02S
Case Study: Adobe - Securing, managing and deploying
enterprise mobile apps
11/17/2016 at 1:00 pm
13 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Questions?
14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Stay connected at communities.ca.com
Thank you.

Pre-Con Ed: How to Provide Mobile Users With a Convenient, Yet Secure, Session Sharing Experience Through OAuth and SAML

  • 1.
    Provide Mobile UserSession Sharing Through OAuth and SAML Sascha Preibisch – Principal Software Architect – CA Technologies DO3X50E DEVOPS
  • 2.
    5 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD For Informational Purposes Only Terms of this Presentation © 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
  • 3.
    6 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Abstract Users of mobile apps like to login to an app once and not get asked for credentials again. In the case of an enterprise that has integrations with third-party web applications it may be difficult to re-use the user session the native app is maintaining. In this workshop we will show how to leverage the CA Mobile API Gateway features to forward the user session using OAuth and SAML. Sascha Preibisch CA Technologies Principal Software Architect
  • 4.
    7 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Agenda WHAT IS THE SCENARIO WHAT ARE THE CHALLENGES WHAT IS CA MOBILE API GATEWAY SWITCHING FROM NATIVE APP TO WEB APPLICATION 1 2 3 4
  • 5.
    8 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD What Is The Scenario Components that are involved API Gateway Backend DB Third-Party Web Application Federated Token Server (SAML) Native App Browser Internet DMZ IDP Device
  • 6.
    9 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Third-Party Web Application API Gateway Backend DB Federated Token Server (SAML) Native App Browser Internet DMZ IDP Device What Are The Challenges User session
  • 7.
    10 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Backend DB Federated Token Server (SAML) DMZ IDP Device What Is CA Mobile API Gateway It is the component that connects it all DMZ Native App Browser Internet CA Mobile API Gateway Third-Party Web Application
  • 8.
    11 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Device Switching From Native App To Web Application From OAuth to SAML DMZ OAuth Switch Context Validate OAuth session Request SAML Token WebSSO Native App Browser Federated Token Server (SAML) Internet CA Mobile API Gateway Third-Party Web Application
  • 9.
    12 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Recommended Sessions SESSION # TITLE DATE/TIME DO3T80S Case Study: Centrica – How CA APIM is enabling Britain’s largest energy provider to know their customer before they open the door 11/16/2016 at 03:00 pm DO3T05S Case Study: LG&E/KU - How Mobile Apps, APIs With Microservices and CA API Management are Helping to Shape the Company’s Future 11/16/2016 at 03:45 pm DO3T02S Case Study: Adobe - Securing, managing and deploying enterprise mobile apps 11/17/2016 at 1:00 pm
  • 10.
    13 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Questions?
  • 11.
    14 © 2016CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Stay connected at communities.ca.com Thank you.

Editor's Notes

  • #2 As you build out your presentation, here are a few dos and don’ts.
  • #9 Third Party Web Application is integrated using SAML Federation Device runs native apps which has a user session API Gateway connects all components IDP Backend could be a hotel reservation system which is connected to a DB
  • #10 The native app has a user token and is associated with the session The session needs to be shared with the third-party web application
  • #11 CA Mobile API Gateway makes connections between all components happen
  • #12 Native app opens web view … … and calls API that takes “target” and an access_token MAG validates access token and issues a SAML token Returns auto-POST form with third-party app as its “action” User is logged in