Skip to content

Revoke endpoint content type is causing failure even though the status code is 200 #2272

Description

@pratik1701

Here is the current Implementation of the userManager and signoutCallback

Image Image

During the Signout Operation we are seeing the revoke call being made with a status code of 200

Image

But the response looks like this

Image

Due to the response not being in a JSON format the call is failing internally in the node package and is hitting the catch block of the sigoutCallback implementation. I have followed a similar issue fix for this here #1650, but I that doesn't seem to fix the issue. Is there a workaround for this issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions