[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNTI0MDY","title","Identity, Authentication and Gaming","state","published","contactAuthorMethod","email","aboutText","

Like most applications, gaming and esports apps typically need some form of authentication and authorization. Depending on the game, a user's account may be anonymous, pseudonymous, or tied to a real world identity.

If a game is single player and single device, authenticating the user may not be required, but once a game is available across devices or can be played with friends or others, game developers need to build authentication. And with authentication comes authorization, where some users may have access to different kinds of functionality.

Auth is critical yet undifferentiated functionality. It's also the front door to your game; if the user can't log in, they can't enjoy what you've worked so hard to build.

While there is a lot of literature out there on different authentication and authorization systems, especially from the perspective of employees/employers, this ebook focuses on specific needs of gaming and esports developers.

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci81NTM0Mg","name","Edited by Dan Moore",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/2344425/medium/DMoore1_SQ_small.jpg?1617054567","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author