Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socializer & MessageFactory improvements #5

Closed
wants to merge 5 commits into from
Closed

Socializer & MessageFactory improvements #5

wants to merge 5 commits into from

Conversation

rndstr
Copy link
Contributor

@rndstr rndstr commented Dec 8, 2011

This fixes a few issues with the gigya communication and adds the socialize.deleteUser API call. See full commit messages for more info.

As for returning the response in Socializer#notifyLogin(), we need that since it is required to set the cookie which is provided by the response.

We also have a method called setCookieFromResponse(\SimpleXMLElement $response) which takes this response and creates a cookie. I can send a PR if you think it should be part of this bundle (and whether it should go into Socializer, or maybe Helper/SocializerHelper).

rndstr and others added 5 commits November 29, 2011 14:41
If `uid` is specified, gigya gets confused and does not accept the request.
Responds with:
    <statusCode>403</statusCode>
    <errorCode>403005</errorCode>
    <statusReason>Forbidden</statusReason>
    <errorMessage>Unauthorized user</errorMessage>
    <errorDetails>Unknown user</errorDetails>
@lsmith77
Copy link

I also just added support for userInfo in notifyLogin. see #6 for details

@rndstr rndstr closed this Sep 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants