The sgcAuth components ship inside the sgcWebSockets trial installer. Download the package for your IDE version and the SGC Auth palette page appears with both clients ready to use: TsgcHTTP_OAuth2_Client and TsgcHTTP_JWT_Client. No separate installer needed.
One installer, one trial. sgcAuth is licensed as a standalone package with the sgcWebSockets Core runtime bundled in, and it is distributed through the same trial download. Install it, open the SGC Auth palette page, and evaluate both clients before you buy.
Trial version works for a limited time on a single workstation. Includes the sgcAuth components.
Trial version works for a limited time on a single workstation. Includes the sgcAuth components.
The OAuth2 and JWT clients need credentials from your own provider or service. WebAuthn needs one extra installer.
Register your application with the OAuth2/OIDC provider you are integrating with to get a Client ID and, for confidential clients, a Client Secret. Google and Microsoft have ready-made presets, TsgcHTTP_OAuth2_Client_Google and TsgcHTTP_OAuth2_Client_Microsoft.
The Authorization Code and PKCE flows open a browser and catch the redirect on a local HTTP listener configured through LocalServerOptions. Make sure the redirect URI you register with the provider matches the IP and port you set.
Decide your algorithm before you start: a shared secret for HMAC (HS256/384/512), or a PEM-encoded private key for RSA or ECDSA (RS256+, ES256+), set on JWTOptions.Algorithms.
Evaluating WebAuthn passkey sign-in needs the sgcCustomIndy add-on installed alongside this trial; it is added to your order automatically if you decide to buy.