Closed anyatibrian closed 1 year ago
@benw-pusher what I don't get is I was able to use the same key to generate pusher users token
@benw-pusher has tested it with post man it only returns 200 status code even when the userID is a fake one and though with wrong secret key it throws the expected error i.e 401
{ "error": "Unauthorized", "description": "Incorrect Secret Key" }
@benw-pusher I think its fine, the issue I had AWS parameter store was returning an older version of the parameter, so I had to delete it and recreate a new one so that the version is consistent through out.
I've not been able to replicate this - the user is deleted as expected. A 401 indicates and incorrect API Key, have you verified this is set correctly?.