omniauth-vis

This small gem will help Rails apps to connect to Vipassana Identity Server (VIS) using Auth2

It provides:

• a strategy file to be used with omniauth gem
• a service to request VIS APIs endpoints

Contact VIS administrators (sebastian.castro@dhamma.org, ryan.johnson@dhamma.org, nilendu.jani@dhamma.org) and provide following informations about your app:

• Name
• Home page url
• Authorized callback urls (example: https://myapp.org/users/auth/vis/callback)

gem add omniauth
gem add omniauth-vis

# config/initializers/omniauth.rb

require "omniauth/strategies/vis"

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :vis, Rails.application.config.vis["app_id"], Rails.application.config.vis["app_secret"]
end

In case you need to work with a custom server, for exmaple a staging server, you can use server_url option

provider :vis, Rails.application.config.vis["app_id"], Rails.application.config.vis["app_secret"], {
  server_url: "https://test.identity.dhamma.org"
}

Vis::Api will implement Oauth2 Client Credentials Flow behind the scene

require "vis/api"
@vis_api = Vis::Api.new(client_id: "xx", client_secret: "xx", server_url: "https://identity.dhamma.org")
@vis_api.get("api_path")
@vis_api.post("api_path", data)

The API documentation can be found at https://identity.dhamma.org/doc. It is automatically generated from the VIS API Users Controller code deployed on production, through the apipie-rails gem.

Example

@vis_api.post("/api/v1/users", {
  email: "email@test.com",
  username: "test",
  encrypted_password: "xxxxxxxxxx"
})

Publish a new version of the gem:

• update the CHANGELOG.md file, see https://keepachangelog.com
• increase gem.version in omniauth-vis.gemspec
• git commit -a "Bump x.y.z"
• git push
• gem build omniauth-vis
• gem push omniauth-vis-x.y.z.gem

To use a non-published-yet code of the gem, e.g., the head of main:

• update your application's Gemfile to use gem "omniauth-vis", git: "git@github.com:dhammaorg/omniauth-vis.git"
• run bundle update omniauth-vis (to run within Docker if you use Docker)
• restart your web server