[fpc-pascal] [Lazarus] FPC's google API units: heads up...

[Michael Van Canneyt]

On Sun, 4 Oct 2026, Wayne Sherman wrote:

> Michael Van Canneyt wrote:
>> For those using the google APIs part of FPC:
>
> Thank you for your continued work on Google API support in FPC. (as
> well as all of your other work on FPC)
> Consider adding service account support to Google Client.
>
> User OAuth - Web apps, mobile apps, desktop software, or CLI tools
> where users log in to grant the app access. Choose User OAuth when
> building a customer-facing product (e.g., "Sign in with Google", an
> app that syncs a user's Google Calendar, or a tool that uploads files
> directly to a user's personal Drive).
>
> Service Accounts - Backend services, cron jobs, CI/CD pipelines,
> microservices, and server-side automation.  Choose a Service Account
> when building automated backend pipelines, server-side background
> processes, or cloud workloads that manage infrastructure or shared
> company resources.  Service Accounts still use OAuth 2.0: Under the
> hood, a service account signs a JSON Web Token (JWT) using its private
> key and exchanges it for a short-lived OAuth 2.0 access token. The
> distinction is that this process is automated and does not require a
> human user to consent.

It is on my todo list, I didn't get around to that 
(I only managed to commit now, the work dates from almost 10 months ago :/).

I'll study your design, thank you.

Michael.