oidc-agent
  • Introduction
  • Quickstart
  • Migrating to oidc-agent 5
  • Installation
    • Linux
    • MacOS
    • Windows
  • Configuration
    • oidc-agent Directory
    • General Configuration
    • Custom Request Parameter
    • Configuration of Providers
    • oidc-agent Integration
    • Agent Forwarding
  • Usage
    • oidc-agent
      • Starting oidc-agent
      • General Usage
      • Detailed Information About All Options
    • oidc-agent-service
    • oidc-keychain
      • General Usage
      • Detailed Information About All Options
    • oidc-gen
      • General Usage
      • Detailed Information About All Options
      • Integrate With Different Providers
        • B2Access
        • EGI
        • Elixir
        • Google
        • HBP
        • Helmholtz AAI
        • IAM (INDIGO/DEEP)
        • KIT
        • Any Other Provider
        • Known Issues
        • Client Configuration Values
    • oidc-add
      • General Usage
      • Detailed Information About All Options
    • oidc-token
      • General Usage
      • Detailed Information About All Options
    • oidc-tokensh
      • General Usage
      • Detailed Information About All Options
    • Other Applications Using oidc-agent
    • Tips
    • oidc-agent-server
  • Windows
    • Installation
  • MAC OS
    • State of Feature Support
    • Installation
  • Security
    • Privilege Separation & Architecture
    • Account Configuration Files
    • Credentials
    • Memory
    • Agent Locking
    • Communication
    • Encryption Passwords
    • Autounload (Lifetime)
    • User Confirmation
    • Tracing
    • seccomp
    • Final Note
  • API
    • liboidc-agent4
    • liboidcagent-go
    • liboidcagent-py
    • IPC-API
Powered by GitBook
On this page
  • Quickstart
  • Advanced options
  • Manual Client registration
  1. Usage
  2. oidc-gen
  3. Integrate With Different Providers

Google

Google does not support dynamic client registration, but there is a preregistered public client so that account configuration generation is as easy as with dynamic client registration.

Quickstart

Example:

$ oidc-gen --pub --issuer https://accounts.google.com/ --flow=device <shortname> 
The following scopes are supported: openid profile
Scopes or 'max' (space separated) [openid profile]: 
[...]
Using a browser on any device, visit:
https://www.google.com/device
[...]
success
The generated account config was successfully added to oidc-agent. You don't have to run oidc-add.

Enter encryption password for account configuration '<shortname>': 
Confirm encryption Password:

Advanced options

Manual Client registration

After the client registration you can download the client configuration as a json file. You can pass this file to oidc-gen using the -f flag. If you don't do this you have to enter the configuration manually (you than have to call oidc-gen with the -m flag).

PreviousElixirNextHBP

Last updated 3 years ago

A client can be registered manually at There is documentation on how to do this at (just the first section "Setting up OAuth 2.0").

https://console.developers.google.com/
https://developers.google.com/identity/protocols/OpenIDConnect