Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-2202

Make it possible to handle opaque access tokens for OIDC

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None

    Description

      The OpenID Connect spec doesn't specify the required format for access tokens. Some OpenID providers like Keycloak and Okta use JWTs for access tokens. Open Liberty uses opaque access tokens by default but can be configured to use JWTs. Google uses opaque access tokens. 

      The current OIDC implementation assumes JWTs for access tokens. We need to update this to handle opaque access tokens as well.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users ELY-2034 Native support for OpenID Connect

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              fjuma1@redhat.com Farah Juma
              fjuma1@redhat.com Farah Juma
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: