wm_okta_helper

Workflow:

• User using an App authenticates through front end using his own Okta credentials.
• User calls App API sending id token
• App uses gem to validate id token

If the wrapper is needed

• App uses gem to get session token
• App calls Wm-mssql-wrapper passing session token
• Wm-mssql-wrapper uses gem to validate session token.

The only App knowledge about Okta is the Figaro parameters.

Add this line to your application's Gemfile:

gem 'wm_okta_helper'

And then execute:

$ bundle

Or install it yourself as:

$ gem install wm_okta_helper

How to use:

      token = WmOktaHelper::AuthenticateApiRequest.new(
        request: request,
        okta_org: Figaro.env.OKTA_ORG,
        okta_domain: Figaro.env.OKTA_DOMAIN,
        okta_client_id: Figaro.env.OKTA_CLIENT_ID
      ).call

Where request is Rails ActionDispatch::Request to request a token.

The response is a signed JSON Web Signature.

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/wm_okta_helper. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

The gem is available as open source under the terms of the MIT License.

Everyone interacting in the wm_okta_helper project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.