map_suite_gis_server_quick_start_guide
Differences
This shows you the differences between two versions of the page.
|
map_suite_gis_server_quick_start_guide [2018/07/20 05:59] admin created |
map_suite_gis_server_quick_start_guide [2018/07/20 14:55] (current) brianr Fixed bold style tagging on client types |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| New GIS Server accounts come with two clients, one of each type, that you can use to quickly get started. | New GIS Server accounts come with two clients, one of each type, that you can use to quickly get started. | ||
| - | * *NativeConfidential* clients have full access to all the APIs you do, including those which manage clients and your user profile. They will authenticate by exchanging their ID and secret key for an identity token. Then, they will use that token to make requests to the GIS Server APIs. These clients are called "NativeConfidential" because their secret key must be kept confidential, and thus they are only suitable for use in native compiled applications or web services where the secret can be kept confidential, out of the hands of users. | + | * **NativeConfidential** clients have full access to all the APIs you do, including those which manage clients and your user profile. They will authenticate by exchanging their ID and secret key for an identity token. Then, they will use that token to make requests to the GIS Server APIs. These clients are called "NativeConfidential" because their secret key must be kept confidential, and thus they are only suitable for use in native compiled applications or web services where the secret can be kept confidential, out of the hands of users. |
| - | * *JavaScript* clients are intended to be used in web applications. They are simpler to use but can only access GIS Server plugins like elevation or the reverse geocoder. To use a JavaScript client, you only need to include the client ID in the URL of the API you are requesting -- no tokens are required. A JavaScript client's ID does not need to be kept confidential, but you should restrict the client so that it can only be used from web domains you control. | + | * **JavaScript** clients are intended to be used in web applications. They are simpler to use but can only access GIS Server plugins like elevation or the reverse geocoder. To use a JavaScript client, you only need to include the client ID in the URL of the API you are requesting -- no tokens are required. A JavaScript client's ID does not need to be kept confidential, but you should restrict the client so that it can only be used from web domains you control. |
| For now, let's use one of the default clients that come with your GIS Server account. For this exercise, we'll choose the Native Confidential client called "Sample Native Client". | For now, let's use one of the default clients that come with your GIS Server account. For this exercise, we'll choose the Native Confidential client called "Sample Native Client". | ||
map_suite_gis_server_quick_start_guide.txt · Last modified: 2018/07/20 14:55 by brianr