Stategy fails with omniauth 1.1 about omniauth-vkontakte HOT 16 CLOSED

The reason is csrf protection in omniauth-oauth2 1.1.0.

Omniauth-facebook has already updated to omniauth-oauth2 1.1.0.
simi/omniauth-facebook@c07e228

We should did the same with omniauth-vkontakte.

from omniauth-vkontakte.

Thanks!

from omniauth-vkontakte.

Currently VKontakte doesn't return state parameter with the code so this won't work until it is fixed on VKontakte side. I wrote to their support about it yesturday, still waiting.

from omniauth-vkontakte.

http://ambivalent.ru/2012/web/oauth-vkontakte-authorisation-no-state-parameter/

from omniauth-vkontakte.

I still get this error, how we can fix it ?

from omniauth-vkontakte.

I don't know. You can still use older versions(< 1.1.0) of omniauth-oauth2.

from omniauth-vkontakte.

Here's the ticket on their support if anyone wants to monitor the issue (and if it can be called a ticket).

from omniauth-vkontakte.

This seems like a bug in Vkontakte.

It works correctly and passes parameter state, only if parameter scope include 'notify'.

from omniauth-vkontakte.

Still no news?

from omniauth-vkontakte.

my previous message

from omniauth-vkontakte.

Any news?

from omniauth-vkontakte.

Парни, как зставить работать гем, не форкая и не изменяя версии зависимостей?

from omniauth-vkontakte.

Видимо, нужно передавать notify в параметре scope, или вообще не задавать этот параметр (там идет notify по умолчанию).

from omniauth-vkontakte.

Заметил, что state стал возвращаться даже без notify в параметре scope. Видимо, поправили.

from omniauth-vkontakte.

@7even, спасибо за инфо

from omniauth-vkontakte.

@7even кстати да… тоже заметил...

from omniauth-vkontakte.