Authorization: ApiKey, Credentials or OAuth 2.0
Last updated
Was this helpful?
Last updated
Was this helpful?
The GeoPard solution is using for the auth procedure.
We recommend checking all authorization options. The choice depends on the particular use case. More usage details are described in every option below.
Authorization with “username” and “password” is one of the possible approaches. In this case, email registration must be done (not using social networks).
Login request example:
AWS Cognito supports OAuth 2.0 protocol for authorization. The general overview is described in the article , the sub-article Authorization Code Grant is the most interesting in the GeoPard case.
Keeping the story short:
Your application has to redirect a user to GeoPard Cognito for login or registration.
Example:
Please, connect with the GeoPard team to receive your application individual client_id
.
The redirected URL will receive a verification code
for the next step.
Your application has to exchange code
for tokens
(access_token
, refresh_token
, id_token
).
Example:
Quick access to WMS and WFS is necessary from time to time. Therefore, it is possible to use the GeoPard API key automatically generated for every account.
apiKey
must be used with /geo
endpoints ONLY.
Usage:
As a geopardApiKey
parameter in the GET request URL.
As an X-API-Key
header in ANY request.
The redirected URL looks like .
The API key can be found in the apiKey
attribute of the "UserData" GraphQL entity. Instructions on how to retrieve apiKey
are provided .