Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-7499

Holder of Key mechanism: HoK Token Verification on Wildfly/JBoss EAP Client Adapter operating as Resource Server

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Obsolete
    • Minor
    • None
    • None
    • Adapter - JEE
    • NEW
    • NEW

    Description

      Resource Server side Holder of Key mechanism support in OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access Tokens, which is one of requirement of Financial API (FAPI) Read and Write API Security Profile (http://openid.net/specs/openid-financial-api-part-2.html#protected-resources-provisions).
      Wildfly/JBoss EAP Client Adapter operating as Resource Server conducts verification of this Certificate Bound Access Tokens (HoK Token).
      Please refer to (https://github.com/keycloak/keycloak-documentation/pull/383) for more discussion.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users KEYCLOAK-6771 Holder of Key mechanism: OAuth 2.0 Certificate Bound Access Tokens

          • 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.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: KEYCLOAK

              People

                Unassigned Unassigned
                tnorimat Takashi Norimatsu (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: