openid

Bienvenue dans le 19e épisode de notre série de podcasts consacrés aux professionnels de l’informatique !

INTERVIEW #19 : Piloter l’identité numérique avec Maxime Hambersin, Senior Director of Product Management International chez DocuSign

L’identité numérique comporte des enjeux majeurs.

Pourtant, le sujet n’est pas toujours clair ! 

• À quoi ça sert ? 
• Comment ça fonctionne ? 
• Quels sont les différents niveaux d’identification ?
• Comment garantir le niveau de confiance ? 
• Comment gérer les risques ?
• Quelle évolution ? 

On va débroussailler tout ça d’un point de vue fonctionnel et technique, et faire un focus plus pratique sur l’utilisation des APIs DocuSign. 

Au micro avec Philippe, Maxime Hambersin, Senior Director of Product Management International chez DocuSign

Pour en savoir plus sur DocuSign : https://www.docusign.fr/ 

Pour se connecter à Maxime sur LinkedIn : https://www.linkedin.com/in/maxime-hambersin-6b30b44/overlay/photo/  

Pour en savoir plus sur DocuSign Identity : https://www.docusign.fr/produits/identify

Plus d’infos sur OpenID Connect : https://openid.net/connect/ 

Neil Madden, author of the API Security in Action book discusses the key requirements needed to secure an API, the risks to consider, models to follow and which task is the most important.

Justin Richer, lead author of the OAuth2 In Action book discusses the key technical features of the OAuth2 authorization protocol and the current best practices for selecting the right parts of it for your use case.

Identity is the missing link that connects all your users, apps, services, and devices to each other and the rest of the world. Christian Smith (@anvilhacks) is founder of Anvil Research (@AnvilResearch) and the creator of Anvil Connect, an open source authorization server built with Node.js to authenticate your users and protect your APIs.

Anvil Connect simplifies security when you have many apps and services to integrate. It acts as a broker between your apps, APIs, and a long list of OAuth providers like Google, Facebook, Twitter, and GitHub. The server works with apps written in any programming language that speaks HTTP. The code is MIT licensed and implements open standards like OAuth 2.0, OpenID Connect, and JSON Web Tokens.

Resources

• Open ID - http://openid.net/

• Anvil Connect - https://github.com/anvilresearch/connect

• Anvil - http://anvil.io/

• Anvil Gitter Channel - https://gitter.im/christiansmith/anvil-connect

• Open ID Connect - http://en.wikipedia.org/wiki/OpenID_Connect

• Single Sign on - http://en.wikipedia.org/wiki/Single_sign-on

• OAuth3 - https://oauth3.org

• JWT (JSON Web Token) - http://jwt.io/

• Let’s Encrypt - https://letsencrypt.org

• Web Crypto -  https://developer.mozilla.org/en-US/docs/Web/API/Window/crypto

• Storm Path - https://stormpath.com/

• Auth0 - https://auth0.com/

• Service Worker - http://www.w3.org/TR/service-workers/

• Ketboot -  https://github.com/substack/keyboot

• scramble.io - https://scramble.io/

• AJ’s article on creating a CSR for Https (tls/ssl) RSA Pems  - https://coolaj86.com/articles/how-to-create-a-csr-for-https-tls-ssl-rsa-pems/

• keybase.io - https://keybase.io/

Panelists

• Erik Isaksen - HTML5 Google Developer Expert & Front End Engineer at Deloitte Digital

• Nick Niemeir - Partner at Good News Everyone

• AJ O’Neal - JavaScript Engineer