OAuth 2.0 Identity and Access Management Patterns
Join the DZone community and get the full member experience.Join For Free
oauth is the most widely known and used authorization framework. there are many service providers like facebook and twitter making it easy to connect with millions of users. from the users perspective is significantly simpler than remember and managing different passwords which is easily manipulated. the book make nice introduction to integration of oauth 2.0 on web applications, desktop and mobile. it also covers various flows and a server side implementation using springmvc. while the examples throughout the book are clean one part really caught my attention:
tokenendpoint .concat("?grant_type=client_credentials") .concat("&client_id=").concat(clientid) .concat("&client_secret=").concat(clientsecret) .concat("&user_id=").concat(user_id)concatenating strings using
string.concatis something i would consider a premature optimization for speed. much cleaner way would be the regular
+based concatenation or even maybe
string.format. in any case that is something that is probably completely irrelevant and off topic but i just can't help it.
what i found really interesting is the chapter titled "additional security with saml", mostly because i did not know there is a thing like this out there let alone used it. saml or security assertion markup language is a xml based protocol for exchange of authentication and authorization data between user and provider where the user can be a provider itself. saml provides single sign-on across multiple domains and identity federation which is useful for many enterprise applications.
a thing to note is that the proofreader did not made a good job since even me with my many typos and grammar error noticed this. this is a problem i had in my book and is an issue with most of the packt publishing books. some folks on reddit and over the "internets" have claimed that this was the case because most of the authors are non-native english speakers. this is is not be the case since there many non-native authors for other publishers and they do a great job so why can't packt?
for me this does not affect the overall impression but i know there are some grammar nazi out there.
one incorrect assumption i made before starting with the book is that it will only cover java related tooling and implementation. there are sections with references to all major programming languages and various tooling support that will assist you independent from your preferred language.
to sum it up the book is an awesome reference for oauth 2.0 and the various pattern for integrating it into your system. i know i will get back to it at some point in the future. you should get it if you expect to do any oauth integration in the future whether it is server or client side.
Published at DZone with permission of Mite Mitreski, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.