{
  "issuer": "https://securetoken.google.com/whosin-258aa",
  "authorization_endpoint": "https://whos-in.app/login",
  "token_endpoint": "https://securetoken.googleapis.com/v1/token",
  "jwks_uri": "https://www.googleapis.com/service_accounts/v1/jwk/securetoken@system.gserviceaccount.com",
  "response_types_supported": ["id_token"],
  "subject_types_supported": ["public"],
  "id_token_signing_alg_values_supported": ["RS256"],
  "grant_types_supported": ["authorization_code", "refresh_token", "implicit"],
  "token_endpoint_auth_methods_supported": ["client_secret_post", "client_secret_basic"],
  "claims_supported": ["aud", "exp", "iat", "iss", "sub", "email", "email_verified", "name", "picture"],
  "scopes_supported": ["openid", "email", "profile"],
  "_note": "Who's In uses Firebase Authentication for user identity: this document describes the Firebase ID tokens Google's Secure Token Service issues for a signed-in Who's In user. It is not an OAuth server for third parties. Agents and integrations use Who's In's own OAuth 2.0 server, described at https://whos-in.app/.well-known/oauth-authorization-server (authorization code grant; scopes read:events, read:attendees, write:events; clients are provisioned by email at api@whos-in.app, no dynamic registration).",
  "contact": "api@whos-in.app"
}
