Mobile and API identity – The New Challenges
 

Mobile and API identity – The New Challenges

on

  • 714 views

With the ever increasing growth of mobile applications and API technologies the topics of identity management, authentication and authorisation are as important as ever. The technologies mean that ...

With the ever increasing growth of mobile applications and API technologies the topics of identity management, authentication and authorisation are as important as ever. The technologies mean that those responsible for identity management and security increasingly have more to consider when deploying and enforcing security. With rapid time to market demands from the business there is much to consider when delivering an open but secure environment for the business and their users.
This session will look at some of the considerations and issues faced in designing and delivering IdM in this emerging space. We will look at how topics such as OAuth, OpenID connect and single sign on play their part in these policies and how governance plays a key role alongside security to protect the environment.

Statistics

Views

Total Views
714
Views on SlideShare
714
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Mobile and API identity – The New Challenges Mobile and API identity – The New Challenges Presentation Transcript

  • Topics§  Define API’s§  How are they being used§  What are the issues§  Whats being used§  One approach
  • Web API =Technology
  • Mobile and API identity – The NewChallengesAran WhiteSolution Architectawhite@layer7.com
  • Is it a Web API?REST/JSON? Yes.SOAP/XML? Yes. HTTP/CSV? Yes.
  • Modern Timeline of Web APIs 2005 2004 2010 First Web 2.0 Programmable web.com Salesforce Conference adds HTTP API launched 2002 54 APIs Amazon API registered. 2005 2000 ebay makes 2008 2012 Salesforce API APIs free Programmable ebay API Programmable web.com has web.com has 2004 2006 1000 registered 7144 registered Flickr API Twitter API APIs APIs Facebook API Google (Maps) Sources: apievangelist.com programmableweb.com API internetarchive.com Steve Yegge Rant oreilly.com
  • How have they grown, or exploded
  • Mobile is driving API publishers
  • The enterprise model:Start with private APIs…
  • …consider going publicin the future
  • API’s From Internal Services§  Create a new shiny API or enable our existing services§  Integration for messages and security§  Internal security verses external security§  Who is using the service the most§  How do we control the use
  • Applications Or Users§  We don’t just want to trust the user what about the application?§  Developers -  On boarding -  Controlling access -  Monitoring -  Managing§  Will you allow application to store user credentials? Long term or per session§  Do we trust all devices or platforms?§  Do we trust Jail broken devices?
  • Single sign on issues§  Multiple Applications§  Multiple devices§  Multiple APIs§  Multiple API providers§  Integration with cloud services
  • How are we tackling this§  New security models§  Oauth§  Open ID connect§  SAML§  Tried and tested approaches -  SSL, Basic Auth, WS Security, XML security -  Standard threats§  Multiple approaches per API§  Brokering between the new world and the existing security
  • OAuth§  Drafts keep changing (or did !!)§  Can be complex§  Picking the correct flow§  Components which do I use.§  Extensions§  Brokering with existing security
  • Open ID Connet§  OAuth based solution for authentication§  Gives access to attributes.§  Giving access to identities outside the enterprise§  Helps scale and agility§  Who is coming through the door§  Tracking and audit
  • SAML§  Still there as a very valid solution§  Supported for federated SSO such as SFDC§  Can be considered heavyweight and complex§  B2B solutions still like SAML§  STS deployments
  • Flexibility is the new challengeSAML PKI LDAP WS-­‐*  
  • The primary API managementchallenge: Balancing Control and Accessibility
  • API publishers want to encourageutilization
  • Low barriers to accessSelf serviceSelf documenting
  • But, API publishers also want torestrict access to APIs
  • Smart rate limitingSecurity enforcementBrand control
  • Architects want API gateways API Gateway API
  • Thank you Aran Whiteawhite@layer7.com