⛔ [DEPRECATED] This repository is no longer actively maintained. You may fork the project but we are no longer accepting pull requests or new issues. You may reach out to [email protected] with questions.
This gem allows you to easily:
- Generate SSO token for creating SSO users / logging them into UserVoice (http://uservoice.com).
- Do 3-legged and 2-legged UserVoice API calls safely without having to worry about the cryptographic details.
Place this in your Gemfile:
gem 'uservoice-ruby'
and run the bundle command or type this in the command line:
gem install uservoice-ruby
Then try one of the examples below.
Prerequisites:
# Suppose your UserVoice site is at http://uservoice-subdomain.uservoice.com/
USERVOICE_SUBDOMAIN = 'uservoice-subdomain'
SSO_KEY = '982c88f2df7257859e8e23423eg87ed' # Admin Console: Settings -> General -> User Authentication
# Define an API client at: Admin Console -> Settings -> Channels -> API
API_KEY = 'oQt2BaunWNuainc8BvZpAm'
API_SECRET = '3yQMSoXBpAwuK3nYHR0wpY6opE341inL9a2HynGF2'
SSO-token can be used to create sessions for SSO users. They are capable of synchronizing the user information from one system to another. Generating the SSO token from SSO key and given uservoice subdomain can be done by calling UserVoice.generate_sso_token method like this:
require 'uservoice-ruby'
sso_token = UserVoice.generate_sso_token(USERVOICE_SUBDOMAIN, SSO_KEY, {
:guid => 1001,
:display_name => "John Doe",
:email => '[email protected]'
}, 5*60) # the token will be valid for 5 minutes (5*60 seconds) by default
# Now this URL will log John Doe in:
puts "https://#{USERVOICE_SUBDOMAIN}.uservoice.com/?sso=#{sso_token}"
With the gem you need to create an instance of UserVoice::Oauth. You get API_KEY and API_SECRET from an API client which you can create in Admin Console -> Settings -> Channels -> API.
require 'uservoice-ruby'
begin
client = UserVoice::Client.new(USERVOICE_SUBDOMAIN, API_KEY, API_SECRET)
# Get users of a subdomain (requires trusted client, but no user)
users = client.get_collection("/api/v1/users")
users.each do |user|
puts "User: \"#{user['name']}\", Profile URL: #{user['url']}"
end
# Now, let's login as [email protected], a regular user
regular_access_token = client.login_as('[email protected]')
# Example request #1: Get current user.
user = regular_access_token.get("/api/v1/users/current.json")['user']
puts "User: \"#{user['name']}\", Profile URL: #{user['url']}"
# Login as account owner
owner_access_token = client.login_as_owner
# Example request #2: Create a new private forum limited to only example.com email domain.
forum = owner_access_token.post("/api/v1/forums.json", :forum => {
:name => 'Ruby Client Private Feedback',
:private => true,
:allow_by_email_domain => true,
:allowed_email_domains => [{:domain => 'example.com'}]
})['forum']
puts "Forum '#{forum['name']}' created! URL: #{forum['url']}"
rescue UserVoice::Unauthorized => e
# Thrown usually due to faulty tokens, untrusted client or if attempting
# operations without Admin Privileges
raise
rescue UserVoice::NotFound => e
# Thrown when attempting an operation to a resource that does not exist
raise
end
If you want to make calls on behalf of a user, but want to make sure he or she actually owns certain email address in UserVoice, you need to use 3-Legged API calls. Just pass your user an authorize link to click, so that user may grant your site permission to access his or her data in UserVoice.
require 'uservoice-ruby'
CALLBACK_URL = 'http://localhost:3000/' # your site
client = UserVoice::Client.new(USERVOICE_SUBDOMAIN, API_KEY, API_SECRET, :callback => CALLBACK_URL)
# At this point you want to print/redirect to client.authorize_url in your application.
# Here we just output them as this is a command-line example.
puts "1. Go to #{client.authorize_url} and click \"Allow access\"."
puts "2. Then type the oauth_verifier from the GET parameter from callback (..&oauth_verifier=[this one]):"
# In a web app we would get the oauth_verifier through a redirect from UserVoice (after a redirection back to CALLBACK_URL).
# In this command-line example we just read it from stdin:
access_token = client.login_with_verifier(gets.match('\w*').to_s)
# All done. Now we can read the current user to know user's email address:
user = access_token.get("/api/v1/users/current.json")['user']
puts "User logged in, Name: #{user['name']}, email: #{user['email']}"