0.0
No commit activity in last 3 years
No release in over 3 years
OmniAuth strategy for nate.com (Korean web portal site which is a conglomerate of Nate, Cyworld and Empas)
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

Runtime

 Project Readme

omniauth-nate

Omniauth strategy for a Korean web portal nate.com which is a conglomerate of Nate, Cyworld and Empas. This allows users to authenticate themselves with their Nate/Cyworld/Empas accounts.

http://www.nate.com

Nate Open Authentication API follows OAuth 1.0 protocol.

http://devsquare.nate.com/openApi/nateAuthAPIGuide

Installation

Add to your Gemfile

gem 'omniauth-nate'

Then bundle install

How to use

Register your application in the following page to obtain consumer key and secret.

http://devsquare.nate.com/

In the confirmation mail, you will additionally receive encryption key and IV required to decrypt the member information retrieved via their GetNateMemberInfo API.

Usage

Along with the usual consumer key and secret, encryption key must be specified.

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :nate, consumer_key, consumer_secret, 
      :encryption => {
        :key => key,                  # Required.
        :iv  => 0.chr * 8,            # Optional. Default: 0.chr * 8
        :algorithm => 'des-ede3-cbc'  # Optional. Default: des-ede3-cbc
      }
end

With Devise

Devise.setup do |config|
  config.omniauth :nate, consumer_key, consumer_secret,
      :encryption => {
        :key => key,                  # Required.
        :iv  => 0.chr * 8,            # Optional. Default: 0.chr * 8
        :algorithm => 'des-ede3-cbc'  # Optional. Default: des-ede3-cbc
      }
end

Authentication Hash

Email address is used as the user identifier.

{
  :provider => 'nate',
  :uid      => 'your-mail@nate.com',
  :info     => {
    :name   => 'your name',
    :email  => 'your-mail@nate.com'
  }
}

Contributing to omniauth-nate

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

License

Copyright (c) 2012 Junegunn Choi

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.