Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Adapter - Node.js
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      1/ Use keycloak-nodejs-connect in order to secure with keycloak your endpoint for your nodejs backend .
      2/ Call that endpoint with a expired token
      3/ You get a 403 error but 'Reason: invalid token (expired)' doesn't show anywhere in server logs. --> difficult to troubleshoot.

      Show
      1/ Use keycloak-nodejs-connect in order to secure with keycloak your endpoint for your nodejs backend . 2/ Call that endpoint with a expired token 3/ You get a 403 error but 'Reason: invalid token (expired)' doesn't show anywhere in server logs. --> difficult to troubleshoot.
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      Hello,
      It is very difficult to troubleshoot 403 errors when using keycloak-nodejs-connect adapter.

      I feel like the reason is that grant-attacher doesn't output in logs or propagate the error in the catch.

      How can I have reasons for 403 somewhere to troubleshoot ? can I submit a PR to display the error in the logs?

      Thanks

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                flapouille Hermine lalvee
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: