• MIT license links to PHP
• Change integration test email

• Copy and adapt README from corbado-php
• Run all code examples from README (make sure they are working)
• Make all code examples fully working (imports, fun main etc.)
• Adapt corbado-php directory structure (introduce services etc.)
• Move config to root and rename to Configuration
• Set version 1.0.0
• Add more Go versions to GitHub matrix (until test users have been implemented)
• Use test users (for email OTP and sms OTP)
• Implement integration test for email OTP validate and sms OTP validate
• Update documentation
• Update wizards
• Restructure version header (rename to X-Corbado-SDK, add "name", "sdkVersion" and "languageVersion" to it)
• Move internal packages to internal/
• Extend README.md with "private client" info

The Corbado GO SDK is commonly referred to as a private client, specifically designed for usage within closed backend applications. This particular SDK should exclusively be utilized in such environments, as it is crucial to ensure that the API secret remains strictly confidential and is never shared.

Why

To get a understanding what SDKs our customers use we need to provide the SDK version in every API request.

TODOS

• Add release version to go binary in some version constant/variable
• Add this version to every request as an additional header: X-Corbado-SDK-Version (we use an additional header because we need to preserve the User-Agent field for the real user agent of the user of our customer)
• Value: "Go SDK (release version)" so for example "Go SDK v0.3.0"

Competitors

• Stytch: https://github.com/stytchauth/stytch-go/blob/main/stytch/stytch.go#L112
• Descope: Could not find a version
• Auth0: https://github.com/auth0/go-auth0/blob/main/internal/client/client.go#L29

• Always implement _ValidationError and _Success case
• Cover more endpoints

• Make real calls to the production BackendAPI
  • Add a new project, name “Corbado Go SDK System testing” (so each SDK will have its on corresponding project)
  • Should be same user/owner as Corbado
• Use GitHub Secrets
  • CORBADO_BACKENDAPI
  • CORBADO_PROJECT_ID
  • CORBADO_APISECRET
• Always use “random values” for fields with unique constraints so system tests can always run in parallel
• Always “clean up” everything after system tests so system tests can run multiple times (and the project stays clean)

https://goreportcard.com/report/github.com/corbado/corbado-go

• Add script to scripts/ folder?
• Implement with bash
• Use oapi-gen
• Use docker container so I do not need to install it locally