X

OpenID Connect: End-user Identity for Apps and APIs (API-University Series)

Product ID : 39224720


Galleon Product ID 39224720
Model
Manufacturer
Shipping Dimension Unknown Dimensions
I think this is wrong?
-
3,199

*Price and Stocks may change without prior notice
*Packaging of actual item may differ from photo shown

Pay with

About OpenID Connect: End-user Identity For Apps And APIs

Product Description Signup and login with a Google, Yahoo, or Microsoft account can be found in more and more web and mobile apps. One login used by many, freeing the end-user from the burden of managing many accounts and passwords. Signup and login to a new app become so smooth and convenient, that end-users are much more likely to try a new app. For us developers of web and mobile apps, these signup and login features are attractive, too: we do not need to manage user credentials, and we get a higher conversion rate resulting in more new customers. In effect, this means cutting costs and increasing the number of new customers for our apps.So how does this feature “Signup and login with Google, Yahoo, or Microsoft” work? It is realized with OpenID Connect, a standardized protocol for sharing end-user data in a secure and controlled manner. Exploring how OpenID Connect works, so we as developers can enjoy its benefits is the subject of this book. This book explains the overall concept of OpenID Connect, so we understand who the actors are, which endpoints and tokens are involved and how these elements interact in so-called flows. These flows tend to get confusing, so we visualize these flows as sequence diagrams, and show how to choose the flow that is appropriate for a given scenario. Using examples, we explore how the tokens are constructed, signed and encrypted with JWT, JWS, and JWE. This is not a programming book, don't expect implementations with a specific programming language or library. Instead, we focus on understanding OpenID Connect on a conceptual level, so we can design and architect apps that work with OpenID Connect. And OpenID Connect is the standard behind creating smooth login and signup experiences, increasing the customer signup rate, and creating highly converting apps. Review "This book is a very thorough guide on a difficult subject. I would highly encourage any software engineer wishing to understand OpenID Connect in greater detail to check this book out." -- software_craftsman "As a software engineer or programmer this is a guide that would help make it easier." -- Anne "Good overview, easy to follow, covers the topic well. A+" -- Charles From the Author The book OpenID Connect perfectly complements the other books in the API-University Series. Check out the other books in this series on OAuth, RESTful API Design, API Architecture, GraphQL, Webhooks, Serverless APIs, and Alexa. From the Back Cover Signup and login with a Google, Yahoo, or Microsoft account can be found in more and more web and mobile apps. One login used by many, freeing the end-user from the burden of managing many accounts and passwords. Signup and login to a new app become so smooth and convenient, that end-users are much more likely to try a new app. For us developers of web and mobile apps, these signup and login features are attractive, too: we do not need to manage user credentials, and we get a higher conversion rate resulting in more new customers. In effect, this means cutting costs and increasing the number of new customers for our apps. So how does this feature "Signup and login with Google, Yahoo, or Microsoft" work? It is realized with OpenID Connect, a standardized protocol for sharing end-user data in a secure and controlled manner. Exploring how OpenID Connect works, so we as developers can enjoy its benefits is the subject of this book. This book explains the overall concept of OpenID Connect, so we understand who the actors are, which endpoints and tokens are involved and how these elements interact in so-called flows. These flows tend to get confusing, so we visualize these flows as sequence diagrams, and show how to choose the flow that is appropriate for a given scenario. Using examples, we explore how the tokens are constructed, signed and encrypted with JWT, JWS, and JWE. This is not a programming book, don't expect implementations with a specific programming language or library. Inste