Google OAuth 2.0 Client-Token used on Server

Question

I plan on accessing the Google Calendar via a Server application and using an authorization token received from the Android client device via AccountManager (full code in this blog post: Link).

Now does anyone know whether or not any problems could arise here? (e.g. Token not refreshable by the server, or token only valid when used by an Android device)

Also, I did request such a token on my phone and also got one (can see it in the debugger, so it was issued by Google), but it doesn't show in my authorized applications neither here nor here.
Is it possible that the token only gets listed after it has been used at least once? (If so, that would be strange imo, since it could be used anytime?)

Answer 1

It is possible. The documentation is here: https://developers.google.com/+/web/signin/server-side-flow

Answer 2

"Now does anyone know whether or not any problems could arise here? "

I've done the opposite (server token on a client) without any problem. Once you have an access token token, you're good to go from anywhere. This is why they expire so quickly.

.

"Is it possible that the token only gets listed after it has been used at least once?"

The Account Permissions page is listing Projects that your user has authorized. So projects appear on that list the moment the user grants access, regardless of whether any tokens have been issued or used.