Chromoting host serveice fails OAuth authentication
897 views
Skip to first unread message
Shunya
Aug 31, 2015, 2:08:01 AM8/31/15
to Chromium-dev
Hello.
I've tried building Chromoting on Windows8.1 Pro, but I have a problem.
When I start a service of Chromoting with my building native applications (e.g. remoting_host.exe, remote_assistance_host.exe), it terminates on the OAuth authentication phase.
I replaced official .exe files and a .dll in "C:\Program Files (x86)\Google\Chrome Remote Desktop\45.0.2454.17\" with mine.
The version of Chromoting is 45.0.2454.17. I think it goes well if the version is the same as Chrome Remote Desktop's.
Attaching a process of remoting_host.exe, I got following massages:
[0831/125602:INFO:oauth_token_getter_impl.cc(154)] Refreshing OAuth token.
[0831/125602:ERROR:oauth_token_getter_impl.cc(115)] OAuth: invalid credentials.
[0831/125602:INFO:remoting_me2me_host.cc(1549)] SendHostOfflineReason: sending INVALID_OAUTH_CREDENTIALS.
[0831/125612:INFO:remoting_me2me_host.cc(1575)] SendHostOfflineReason failed.
On building, I followed the ChromotingBuildInstruction(https://code.google.com/p/chromium/wiki/ChromotingBuildInstructions).
I couldn't find how to generate API key in this document, so I generated the key by "Add credentials→API key→Browser key".
Also I found a following topic.
google_api_key.
https://groups.google.com/a/chromium.org/forum/#!searchin/chromium-dev/google_api_key/chromium-dev/SjLQ3VWRXds/AHp36oD-4XYJ
According to this topic, building Chromoting needs an "Installed Application - Other" key (GOOGLE_CLIENT_ID_REMOTING_HOST, GOOGLE_CLIENT_SECRET_REMOTING_HOST).
So I've created a new OAuth2 Client ID as "Other" and defined GOOGLE_CLIENT_ID_REMOTING_HOST and GOOGLE_CLIENT_SECRET_REMOTING_HOST in google_api_keys.cc directly.
But the problem have not been solved.
What should I do to solve this problem?
Please tell me.
I've tried building Chromoting on Windows8.1 Pro, but I have a problem.
When I start a service of Chromoting with my building native applications (e.g. remoting_host.exe, remote_assistance_host.exe), it terminates on the OAuth authentication phase.
I replaced official .exe files and a .dll in "C:\Program Files (x86)\Google\Chrome Remote Desktop\45.0.2454.17\" with mine.
The version of Chromoting is 45.0.2454.17. I think it goes well if the version is the same as Chrome Remote Desktop's.
Attaching a process of remoting_host.exe, I got following massages:
[0831/125602:INFO:oauth_token_getter_impl.cc(154)] Refreshing OAuth token.
[0831/125602:ERROR:oauth_token_getter_impl.cc(115)] OAuth: invalid credentials.
[0831/125602:INFO:remoting_me2me_host.cc(1549)] SendHostOfflineReason: sending INVALID_OAUTH_CREDENTIALS.
[0831/125612:INFO:remoting_me2me_host.cc(1575)] SendHostOfflineReason failed.
On building, I followed the ChromotingBuildInstruction(https://code.google.com/p/chromium/wiki/ChromotingBuildInstructions).
I couldn't find how to generate API key in this document, so I generated the key by "Add credentials→API key→Browser key".
Also I found a following topic.
google_api_key.
https://groups.google.com/a/chromium.org/forum/#!searchin/chromium-dev/google_api_key/chromium-dev/SjLQ3VWRXds/AHp36oD-4XYJ
According to this topic, building Chromoting needs an "Installed Application - Other" key (GOOGLE_CLIENT_ID_REMOTING_HOST, GOOGLE_CLIENT_SECRET_REMOTING_HOST).
So I've created a new OAuth2 Client ID as "Other" and defined GOOGLE_CLIENT_ID_REMOTING_HOST and GOOGLE_CLIENT_SECRET_REMOTING_HOST in google_api_keys.cc directly.
But the problem have not been solved.
What should I do to solve this problem?
Please tell me.
Shunya
Aug 31, 2015, 6:11:13 AM8/31/15
to Chromium-dev
I've solved this problem by myself !
I had used the service installed by the official installer.
So it had used a refresh token in "C:\ProgramData\Google\Chrome Remote Desktop\host.json".
But Chromoting requires "C:\ProgramData\Chromoting\host.json".
Therefore the refresh token didn't have matched needed one.
I changed the argument of service's "Path to executable" with "--host-config="C:\ProgramData\Chromoting\host.json".
Then the problem had been solved !
2015年8月31日月曜日 15時08分01秒 UTC+9 Shunya:
I had used the service installed by the official installer.
So it had used a refresh token in "C:\ProgramData\Google\Chrome Remote Desktop\host.json".
But Chromoting requires "C:\ProgramData\Chromoting\host.json".
Therefore the refresh token didn't have matched needed one.
I changed the argument of service's "Path to executable" with "--host-config="C:\ProgramData\Chromoting\host.json".
Then the problem had been solved !
2015年8月31日月曜日 15時08分01秒 UTC+9 Shunya:
Reply all
Reply to author
Forward
0 new messages