![]() A scope actually describes the part of the API (or APIs) that you want your app to have access to. Right before you ask from users to sign in, it’s important to determine the scopes of the API you want to access. The Sign-In SDK contains a special view controller for this purpose, so there’s no need to call any external browser or implement in-app web views. In order for users to sign in with their Google account into an app, it’s required to provide them with an interface to do so. If you want to read more about the OAuth 2.0 protocol, Google provides a nice documentation page for this reason. After a successful sign in, every iOS app can use the access token (and refresh token) to make authorized requests, and most importantly developers can focus on the application logic only. Things have dramatically changed, as the Sign-In button implements and performs the whole OAuth process behind the scenes. Trust me, that was a great hassle, as there were several steps needed to be implemented under certain conditions until the desired access and refresh tokens to be fetched. Before the Sign-In SDK becomes available, every developer who wanted to allow user authentication in iOS applications and subsequently to perform authorized requests to specific APIs had to manually implement the OAuth 2.0 protocol flow following the rules defined by Google.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |