User Tools

Site Tools


thinkgeo_cloud_keys_guideline

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
thinkgeo_cloud_keys_guideline [2019/02/06 17:08]
benbai [Apply a ThinkGeo Cloud Client Key]
thinkgeo_cloud_keys_guideline [2019/02/06 21:26] (current)
benbai
Line 1: Line 1:
-=====Apply a ThinkGeo Cloud Client Key ===== +=====Use a ThinkGeo Cloud Client Key ===== 
-client ​is how you can enable your application or website to use ThinkGeo Cloud resources on your behalf. ​ You can have as many clients ​in your account as you like. Different application or website can use different ​clients ​or share the same one. +ThinkGeo Cloud Client Key is how you can enable your application or website to use ThinkGeo Cloud resources on your behalf. ​ You can have as many client keys in your account as you like. Different application or website can use different ​keys or share the same one.  
 + 
 + 
 + 
 +====Use the Pre-Generated Test Keys ==== 
 +Two test clients have been pre-generated for a new ThinkGeo Account. Here is how to get them:  
 + 
 +First, Log in to the ThinkGeo Cloud with your ThinkGeo account, the same one you can use to access our [[http://​community.thinkgeo.com/​|community forums]]. ​ If you don't have a ThinkGeo account yet, [[https://​singlepoint.thinkgeo.com/​registration|sign up for one here]]. 
 + 
 +Then, visit the ThinkGeo Cloud web console login page at https://​cloud.thinkgeo.com/​login.html and click the "Login with ThinkGeo Account"​ button. 
 + 
 +[[https://​cloud.thinkgeo.com/​login.html|{{:​thinkgeo_cloud_login_page.png?​nolink&​500}}]] 
 + 
 + 
 +Once logged in, click on the "​Clients"​ button on the menu bar. 
 + 
 +{{::​thinkgeo_cloud_dashboard.png}} 
 + 
 +New ThinkGeo Cloud accounts come with two clients, one is NativeConfidential and the other is JavaScript, which you can use to quickly get started. Click on the green **Show Keys** button and the ClientId & Client Secret (for NativeConfidential Key) or JavaScript API Key (for JavaScript Client Key) will show up and ready to use. Hit the blue pencil button on the far right to modify it.  
 + 
 +{{::​thinkgeo_cloud_clientlist.png}}
  
 ====NativeConfidential and JavasScript Client Keys==== ====NativeConfidential and JavasScript Client Keys====
-There are two different kinds of clients ​you can apply for your application:​ NativeConfidential,​ which is intended to be used in natively compiled applications or web services; and JavaScript, which is intended to be used in web applications. Here below is the comparison between the two. +There are two different kinds of client keys you can apply for your application:​ NativeConfidential,​ which is intended to be used in natively compiled applications or web services; and JavaScript, which is intended to be used in web applications. Here below is the comparison between the two. 
 === === === ===
  
Line 25: Line 45:
 Intended to be used in web applications. ​ Intended to be used in web applications. ​
 </​div>​ </​div>​
- 
 === Accessibilities to the Restful APIs === === Accessibilities to the Restful APIs ===
  
Line 34: Line 53:
 <div dokuteaser>​ <div dokuteaser>​
 Can only access ThinkGeo Cloud plugins like elevation or the reverse geocoder. ​ Can only access ThinkGeo Cloud plugins like elevation or the reverse geocoder. ​
 +</​div>​
 +
 +=== What does its key look like===
 +<div dokuteaser>​
 +Two Base64 encoded string, one is for Client ID and the other is for Client Secret. ​
 +</​div>​
 +
 +<div dokuteaser>​
 +One Base64 encoded string as APIKey.  ​
 </​div>​ </​div>​
  
Line 43: Line 71:
  
 <div dokuteaser>​ <div dokuteaser>​
-A JavaScript client'​s ID does not need to be kept confidential since they are intended for use in browser-based applications where a secret cannot be kept secure. ​but you should restrict the client so that it can only be used from web domains you control.  ​+A JavaScript client'​s ID does not need to be kept confidential since they are intended for use in browser-based applications where a secret cannot be kept secure. ​But you should restrict the client so that it can only be used from web domains you control.  ​
 </​div>​ </​div>​
  
Line 55: Line 83:
 You only need to include the client ID in the URL of the API you are requesting – no tokens are required You only need to include the client ID in the URL of the API you are requesting – no tokens are required
 </​div>​ </​div>​
- 
-====Use the Pre-Generated Test Keys ==== 
-You can log in to the ThinkGeo Cloud with your ThinkGeo account, the same one you can use to access our [[http://​community.thinkgeo.com/​|community forums]]. ​ If you don't have a ThinkGeo account yet, [[https://​singlepoint.thinkgeo.com/​registration|sign up for one here]]. 
- 
-Then, visit the ThinkGeo Cloud web console login page at https://​cloud.thinkgeo.com/​login.html and click the "Login with ThinkGeo Account"​ button. 
- 
-Once logged in, click on the "​Clients"​ button on the menu bar. 
- 
-{{::​thinkgeo_cloud_dashboard.png}} 
- 
-New ThinkGeo Cloud accounts come with two clients, one is NativeConfidential and the other is JavaScript, which you can use to quickly get started. Click on the green **Show Keys** button and the ClientId & Client Secret (for NativeConfidential Key) or JavaScript API Key (for JavaScript Client Key) will show up and ready to use. Hit the blue pencil button on the far right to modify it.  
- 
-{{::​thinkgeo_cloud_clientlist.png}} 
  
 ====Create a New Client==== ====Create a New Client====
Line 110: Line 125:
 {{::​thinkgeo_cloud_api_test_page.png?​400}} {{::​thinkgeo_cloud_api_test_page.png?​400}}
  
-Available Authorizations window shows up and you can then input either a NativeConfidential(Client ID and Client Secret) or a JavaScript Key, and click the "​Authorize"​ button to finish authorization. ​+Available Authorizations window shows up and you can then input either a NativeConfidential(Client ID and Client Secret ​combination) or a JavaScript Key, and click the "​Authorize"​ button to finish authorization. ​
  
 {{::​thinkgeo_cloud_available_authorizations_native_confidential.png?​400}} {{::​thinkgeo_cloud_available_authorizations_native_confidential.png?​400}}
Line 118: Line 133:
 ====Advanced Usages ==== ====Advanced Usages ====
  
-To make it even more secure, you can even create your own Token server serving ​tokens to your own clients. In this way, your clients don't need to hold NativeConfidential Keys at all but only talk to your own server to get the token. It's your token server that holds NativeConfidential Keys (ClientId/​ClientSecret) and talks to ThinkGeo to get the tokens. It's not hard to accomplish with ThinkGeo's APIs+To make it even more secure, you can even create your own Token server serving your clients. In this way, your application doesn't need to hold NativeConfidential Keys and talk to ThinkGeo Server, instead it just talk to your own server to get the token. It's your token server that holds NativeConfidential Keys (ClientId/​ClientSecret) and get the tokens ​from ThinkGeo. ​
  
thinkgeo_cloud_keys_guideline.1549472920.txt.gz · Last modified: 2019/02/06 17:08 by benbai