Complete GEE OAuth flow without requiring a JWT — for clients (e.g. the QGIS

plugin) that open the browser but cannot receive the Google redirect directly.

The user ID is resolved from the state parameter via the reverse mapping written by the initiate endpoint, so no authentication header is needed.

Content-Type: application/json

Request Body:

• code (str, required): Authorization code from Google
• state (str, required): CSRF state token from the initiate call

Response:

{
  "data": {
    "status": "connected",
    "gee_google_email": "user@gmail.com",
    "client_type": "qgis_plugin"
  }
}

client_type reflects the originating client ("qgis_plugin" or null) and is used by the callback page to show a context-appropriate success message.

Error Responses:

• 400: Missing/invalid code or state
• 404: User not found
• 500: Token exchange or save failure