use OmniAuth::Builder do provider :vkontakte, ENV['API_KEY'], ENV['API_SECRET'] end
You can configure several options, which you pass in to the
provider method via a
scope: A comma-separated list of permissions you want to request from the user. Read the Vkontakte docs for more details
display: The display context to show the authentication page. Options are:
For example, to request
photos permissions and display the authentication page in a popup window:
use OmniAuth::Builder do provider :vkontakte, ENV['API_KEY'], ENV['API_SECRET'], :scope => 'friends,audio,photos', :display => 'popup' end
Update to omniauth-oauth2 1.1.0
Application raise "invalid credensials" when login. The reason is csrf protection in omniauth-oauth2 1.1.0.
Vkontakte doesn't return
state parameter with the code, if the
scope doesn't include
The solution is to specify at least the
notify in parameter
scope, like so:
use OmniAuth::Builder do provider :vkontakte, ENV['API_KEY'], ENV['API_SECRET'], :scope => 'notify' end
Tested with the following Ruby versions:
- MRI 1.9.3
- MRI 1.8.7
Contributing to omniauth-vkontakte
- Fork, fix, then send me a pull request.
Copyright (c) 2011, 2012 Anton Maminov
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.