AM as OIDC Provider for Kubernetes Authentication

This topic has 0 replies, 1 voice, and was last updated 3 years, 2 months ago by [email protected].

  • Author
  • #26634


    I am looking for information if AM can be used as OIDC Identity Provider for Kubernetes API Authentication (id_token JWT). While I could find documentation on CoreOS DEX , TREMOLO OpenUnison and Keylock. There is no [google] documented information on use of ForgeRock AM.

    As per the documentations for an identity provider to work with Kubernetes it must:
    Support OpenID connect discovery; not all do.
    Run in TLS with non-obsolete ciphers
    Have a CA signed certificate (even if the CA is not a commercial CA or is self signed)

    which seem can be met using AM & IDM ? (

    Appreciate direction or if I am missing some basic here ?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?