Private channel authorization response problem

[lukeredpath]

Im attempting to use this library with an application backed by Parse.com, and am running into an issue with the authorization flow.

Parse wraps all of its cloud code responses in a "result" key, so the auth response from the server looks like {"result": {"auth": }}.

This seems to be keeping authorization attempts from working. Any way to specify how the server response should be parsed?

PS: I'm new to pusher, so there's a distinct possibility that in approaching this the wrong way.

Thanks!

[lukeredpath]

Hmm, unfortunately the fundamental issue here is that Parse isn't returning the correct response for a Pusher authentication payload.

My work on custom authentication methods will probably solve this problem but its not a small change. In the meantime, I have an idea for a small extension to the Pusher delegate protocol that might fix this. I'll update this issue once I've had a chance to look at it.

[lukeredpath]

@jalehman if you're able to use the above branch (this should be easy enough if you're using CocoaPods), you'll see I've added a new delegate method that can be used to modify the auth response and return something in the correct format.

In your case, you would implement it like this:

 - (NSDictionary *)pusher:(PTPusher *)pusher authorizationPayloadFromResponseData:(NSDictionary *)responseData
{
    return responseData[@"result"];
}

Please let me know how you get on.

[jalehman]

@lukeredpath That did the trick! Thanks a ton for the quick response and fix (despite the fault being with Parse).

[lukeredpath]

Thanks. I'm going to leave this open until I've merged it.