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
  1. Usage
  2. oidc-gen
  3. Integrate With Different Providers

B2Access

PreviousIntegrate With Different ProvidersNextEGI

Last updated 4 years ago

B2ACCESS does not support dynamic client registration and you have to register a client manually at or (depending on the issuer url).

There is documentation on how to do this at

After the client registration call oidc-gen with the -m flag and enter the required information.

Note: In general for B2ACCESS and UNITY OPs the following information may be helpful (depending on the instance you use)

  • User Name is the OIDC client_id (you can choose it)

  • Password is the OIDC client_secret (you choose it)

  • Email Address is an email address for contacting the admin of the service

  • Service Security Contact is the security responsible of the service. This

    may be additional people, for example in a hosted VM setup

  • Site Security Contactis your computer centre security contact. Typically

    your CERT.

  • Service PP URL: This is your Privacy Policy (PP). Required by law.

    Find a

  • The well_known configuration of login is here:

    <b2access-hostname>/oauth2/.well-known/openid-configuration
https://b2access.eudat.eu/
https://b2access-integration.fz-juelich.de/
https://unity.eudat-aai.fz-juelich.de/
https://eudat.eu/services/userdoc/b2access-service-integration#UserDocumentation-B2ACCESSServiceIntegration-HowtoregisteranOAuthclient
PP template here