Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-1026

Improve HTTP 401 response in swatch-contracts

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      As a user of the swatch-contracts API, I'd like to be able to distinguish between cases when auth was not provided, and when auth failed. This is possible by following https://quarkus.io/guides/security-built-in-authentication-support-concept#how-to-customize-authentication-exception-responses 

      • current behavior is 401 with no details
      • expected behavior: 
        • both human readable message, and machine-readable code

              Unassigned Unassigned
              khowell@redhat.com Kevin Howell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: