Uploaded image for project: 'Quarkus Documentation'
  1. Quarkus Documentation
  2. QDOCS-93

[security.adoc & security-builtin-authentication.adoc] Create a how-to.adoc for a general advise on the authentication mechanism selection

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Upstream-docs
    • 10
    • False
    • Hide

      None

      Show
      None
    • False
    • Quarkus Upstream Docs Sprint 1, Quarkus Upstream Docs Sprint 2, Quarkus Upstream Docs Sprint 3

      Create a dedicated section about general advise on the authentication mechanism selection - for example, we can have a table matching requirements with suggested authentication mechanisms, like:

      • Token authentication required <-> OIDC or JWT authentication mechanism, where OIDC and JWT being links to corresponding OIDC and JWT guides.
         
      • Or username and password authentication <> Basic or Form, or Single SignOn <> OIDC, etc.
      • ex Name and password: Basic, Form where Basic and Form are links, Bearer access token: OIDC, Client Certificate: MTLS, etc

      In other words:
      Create a table like that one which will provide a general match between the auth requirement and the actual mechanism which can be used

       

       

              mmaler@redhat.com Michal Maléř
              mpurcell@redhat.com Michelle Purcell
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: