auth0 5.18.1 → 5.19.0

data/.github/workflows/semgrep.yml

@@ -1,40 +0,0 @@
-name: Semgrep
-
-on:
-  merge_group:
-  pull_request:
-    types:
-      - opened
-      - synchronize
-  push:
-    branches:
-      - master
-  schedule:
-    - cron: '30 0 1,15 * *'
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/master' }}
-
-jobs:
-  run:
-    name: Check for Vulnerabilities
-    runs-on: ubuntu-latest
-
-    container:
-      image: returntocorp/semgrep
-
-    steps:
-      - if: github.actor == 'dependabot[bot]' || github.event_name == 'merge_group'
-        run: exit 0 # Skip unnecessary test runs for dependabot and merge queues. Artifically flag as successful, as this is a required check for branch protection.
-
-      - uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.head.sha || github.ref }}
-
-      - run: semgrep ci
-        env:
-          SEMGREP_APP_TOKEN: ${{ secrets.SEMGREP_APP_TOKEN }}

data/.github/workflows/snyk.yml

@@ -1,40 +0,0 @@
-name: Snyk
-
-on:
-  merge_group:
-  workflow_dispatch:
-  pull_request:
-    types:
-      - opened
-      - synchronize
-  push:
-    branches:
-      - master
-  schedule:
-    - cron: "30 0 1,15 * *"
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/master' }}
-
-jobs:
-  check:
-    name: Check for Vulnerabilities
-    runs-on: ubuntu-latest
-
-    steps:
-      - if: github.actor == 'dependabot[bot]' || github.event_name == 'merge_group'
-        run: exit 0 # Skip unnecessary test runs for dependabot and merge queues. Artifically flag as successful, as this is a required check for branch protection.
-
-      - uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.head.sha || github.ref }}
-
-      - run: npm install -g snyk
-
-      - run: snyk test
-        env:
-          SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}

data/.github/workflows/test.yml

@@ -1,69 +0,0 @@
-name: Build and Test
-
-on:
-  merge_group:
-  workflow_dispatch:
-  pull_request:
-    branches:
-      - master
-  push:
-    branches:
-      - master
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/master' }}
-
-env:
-  CACHE_KEY: "${{ github.ref }}-${{ github.run_id }}-${{ github.run_attempt }}"
-
-jobs:
-  configure:
-    name: Configure Build Matrix
-    runs-on: ubuntu-latest
-
-    outputs:
-      matrix: ${{ steps.set-matrix.outputs.matrix }}
-
-    steps:
-      - uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.head.sha || github.ref }}
-
-      - id: set-matrix
-        run: echo "matrix=$(jq -c . < ./.github/workflows/matrix.json)" >> $GITHUB_OUTPUT
-
-  unit:
-    needs: configure
-
-    name: Run Unit Tests
-    runs-on: ubuntu-latest
-
-    strategy:
-      matrix: ${{ fromJson(needs.configure.outputs.matrix) }}
-
-    env:
-      DOMAIN: example.auth0.dev
-      CLIENT_ID: example-client
-      CLIENT_SECRET: example-secret
-      MASTER_JWT: example-jwt
-      BUNDLE_PATH: vendor/bundle
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-
-      - name: Configure Ruby
-        uses: ./.github/actions/setup
-        with:
-          ruby: ${{ matrix.ruby }}
-
-      - name: Run tests
-        run: bundle exec rake test
-
-      - name: Upload coverage
-        if: matrix.ruby == '3.2' || matrix.ruby == '3.3'
-        uses: codecov/codecov-action@671740ac38dd9b0130fbe1cec585b89eea48d3de # pin@5.5.2

data/.gitignore

@@ -1,18 +0,0 @@
-bin/
-!examples/ruby-on-rails-api/bin/
-vendor/
-doc/
-.DS_Store
-.ruby-version
-coverage
-*.gem
-.ruby-gemset
-*.swp
-*.swo
-spec/auth0.yml
-.env
-/.yardoc/checksums
-/.yardoc/complete
-/.yardoc/object_types
-/.yardoc/objects/root.dat
-/.yardoc/proxy_types

data/.rspec

@@ -1,3 +0,0 @@
---color
---format Fuubar
---color

data/.rubocop.yml

@@ -1,10 +0,0 @@
-inherit_from: .rubocop_todo.yml
-require:
-  - rubocop-rails
-Rails:
-  Enabled: true
-AllCops:
- Exclude:
-   - bin/**/*
-   - vendor/**/*
-   - auth0.gemspec

data/.rubocop_todo.yml

@@ -1,5 +0,0 @@
-Metrics/MethodLength:
-  Max: 15
-
-Metrics/LineLength:
-  Max: 121

data/.semgrepignore

@@ -1,6 +0,0 @@
-.bundle/
-.circleci/
-.devcontainer/
-.github/
-examples/
-spec/

data/.shiprc

@@ -1,8 +0,0 @@
-{
-  "files": {
-    "lib/auth0/version.rb": [],
-    ".version": []
-  },
-  "prebump": "bundle install && bundle exec rake test",
-  "postbump": "bundle update"
-}

data/.snyk

@@ -1,17 +0,0 @@
-ignore:
-  SNYK-RUBY-RACK-1061917:
-    - rubocop-rails > rack:
-      reason: No direct upgrade available
-      expires: "2023-11-02T12:00:00.000Z"
-    - dotenv-rails > railties > actionpack > rack:
-        reason: No direct upgrade available
-        expires: "2023-11-02T12:00:00.000Z"
-    - dotenv-rails > railties > actionpack > rack-test:
-        reason: No direct upgrade available
-        expires: "2023-11-02T12:00:00.000Z"
-  snyk:lic:rubygems:json:Ruby:
-    - '*':
-        reason: Ruby standard library gem, Ruby license is acceptable
-  snyk:lic:rubygems:reline:Ruby:
-    - '*':
-        reason: Ruby standard library gem, Ruby license is acceptable

data/CODE_OF_CONDUCT.md

@@ -1,3 +0,0 @@
-# Code of Conduct
-
-Please see [Auth0's code of conduct guidelines](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md) for information on contributing to this repo.

data/DEPLOYMENT.md

@@ -1,61 +0,0 @@
-# Releasing the gem
-
-## Credentials set up
-
-Make sure you have access in https://rubygems.org/gems/auth0/ and that your Ruby Gems tokens are set in `~/.gem/credentials`.
-
-In order to generate the required changelog entry, define an environment variable `GITHUB_READ_TOKEN` with a Github API token that has READ access to `repo:public_repo`. You can generate a Github API Token [here](https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token).
-
-Create a new Github Milestone with the version name prefixed with `v`. i.e. `v4.10.2`. Assign every Issue and Pull Request to be included on this release to that Milestone, and tag them with the `CH:xxxxxx` labels, depending on the type of change fixed or introduced there.
-
-Finally, follow the next steps:
-
-```bash
-# Install gems for exec commands
-bundle install
-
-# Run all tests
-bundle exec rake test
-
-# Create a release branch
-git checkout master
-git pull
-git checkout -b release-X.X.X
-git push --set-upstream origin release-X.X.X
-
-# Update the version number
-# This will create a commit with the new version
-bundle exec gem bump --version X.X.X
-
-# Make sure the Gemfile.lock is up-to-date
-bundle update
-git commit -am "Update gems"
-
-# Generate the changelog
-github_changelog_generator -t $GITHUB_READ_TOKEN
-# ... or similar.
-# Review the changelog
-# Remove "unreleased" section
-# Make sure the tags are ordered
-
-# Commit, push, and create a PR for this release
-git commit -am "Update CHANGELOG.md"
-git push
-
-# Add related milestone
-# Create PR on GitHub and assign for review
-# Merge/rebase and delete branch once approved
-
-# Create and add a tag
-git checkout master
-git pull
-bundle exec gem tag
-git push origin vX.X.X
-# Create a new release from this tag on GitHub using markdown from the changelog
-
-# Make sure you are an author for this gem here https://rubygems.org/gems/auth0/
-# Rubygems token can be updated in ~/.gem/credentials
-bundle exec gem release
-```
-
-The steps above were tested with Ruby `v2.5.7`.

data/DEVELOPMENT.md

@@ -1,35 +0,0 @@
-# Development
-
-In order to set up the local environment you'd have to have Ruby installed and a few global gems used to run and record the unit tests. A working Ruby version can be taken from the [CI script](/.circleci/config.yml). At the moment of this writting we're using Ruby `2.5.7`.
-
-> It is expected that every Pull Request introducing a fix, change or feature contains enough test coverage to assert the new behavior.
-
-## Running the tests
-
-Install the gems required for this project.
-
-```bash
-bundle install
-```
-
-Finally, run the tests.
-
-```bash
-bundle exec rake test
-```
-
-### Running only unit tests
-
-You can run only the unit tests and ignore the integration tests by running the following:
-
-```bash
-bundle exec rake spec
-```
-
-### Running only integration tests
-
-You can run only the unit tests and ignore the integration tests by running the following:
-
-```bash
-bundle exec rake integration
-```

data/Dockerfile

@@ -1,5 +0,0 @@
-FROM ruby:2.5
-
-WORKDIR /home/app
-
-COPY . /home/app

data/EXAMPLES.md

@@ -1,222 +0,0 @@
-# Examples using ruby-auth0
-
-## Build a URL to Universal Login Page
-
-```ruby
-require 'auth0'
-
-client = Auth0Client.new(
-  client_id: ENV['AUTH0_RUBY_CLIENT_ID'],
-  client_secret: ENV['AUTH0_RUBY_CLIENT_SECRET'],
-  domain: ENV['AUTH0_RUBY_DOMAIN'],
-)
-
-client.authorize_url 'http://localhost:3000'
-
-> => #<URI::HTTPS https://YOUR_DOMAIN/authorize?client_id=YOUR_CLIENT_ID&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A3000>
-
-```
-
-## Management API Client
-
-As a simple example of how to get started with the management API, we'll create an admin route to point to a list of all users from Auth0:
-
-```ruby
-# config/routes.rb
-Rails.application.routes.draw do
-  # ...
-  get 'admin/users', to: 'all_users#index'
-  # ...
-end
-```
-
-... and a Controller to handle that route:
-
-```ruby
-# app/controllers/all_users_controller.rb
-require 'auth0'
-
-class AllUsersController < ApplicationController
-  # Get all users from Auth0 with "auth0" in their email.
-  def index
-    @params = {
-      q: "email:*auth0*",
-      fields: 'email,user_id,name',
-      include_fields: true,
-      page: 0,
-      per_page: 50
-    }
-    @users = auth0_client.users @params
-  end
-
-  private
-
-  # Setup the Auth0 API connection.
-  def auth0_client
-    @auth0_client ||= Auth0Client.new(
-      client_id: ENV['AUTH0_RUBY_CLIENT_ID'],
-      client_secret: ENV['AUTH0_RUBY_CLIENT_SECRET'],
-      domain: ENV['AUTH0_RUBY_DOMAIN'],
-      api_version: 2,
-      timeout: 15 # optional, defaults to 10
-    )
-  end
-end
-```
-
-In this example, we're using environment variables to store the values needed to connect to Auth0 and authorize. The `token` used above is an API token for the Management API with the scopes required to perform a specific action (in this case `read:users`). These tokens can be [generated manually](https://auth0.com/docs/api/management/v2/tokens#get-a-token-manually) using a test Application or with the [Application](https://manage.auth0.com/#/applications) being used for your project.
-
-Finally, we'll add a view to display the results:
-
-```ruby
-# app/views/all_users/index.html.erb
-<h1>Users</h1>
-<%= debug @params %>
-<%= debug @users %>
-```
-
-This should show the parameters passed to the `users` method and a list of users that matched the query (or an empty array if none).
-
-## Organizations
-
-[Organizations](https://auth0.com/docs/organizations) is a set of features that provide better support for developers who build and maintain SaaS and Business-to-Business (B2B) applications.
-
-Note that Organizations is currently only available to customers on our Enterprise and Startup subscription plans.
-
-### Logging in with an Organization
-
-Configure the Authentication API client and pass your Organization ID or name to the authorize url:
-
-```ruby
-require 'auth0'
-
-@auth0_client ||= Auth0Client.new(
-  client_id: '{YOUR_APPLICATION_CLIENT_ID}',
-  client_secret: '{YOUR_APPLICATION_CLIENT_SECRET}',
-  domain: '{YOUR_TENANT}.auth0.com',
-  organization: "{YOUR_ORGANIZATION_ID_OR_NAME}"
-)
-
-universal_login_url = @auth0_client.authorization_url("https://{YOUR_APPLICATION_CALLBACK_URL}")
-
-# redirect_to universal_login_url
-```
-
-### Accepting user invitations
-
-Auth0 Organizations allow users to be invited using emailed links, which will direct a user back to your application. The URL the user will arrive at is based on your configured `Application Login URI`, which you can change from your Application's settings inside the Auth0 dashboard. When they arrive at this URL, a `invitation` and `organization` query parameters will be provided
-
-```ruby
-require 'auth0'
-
-@auth0_client ||= Auth0Client.new(
-  client_id: '{YOUR_APPLICATION_CLIENT_ID}',
-  client_secret: '{YOUR_APPLICATION_CLIENT_ID}',
-  domain: '{YOUR_TENANT}.auth0.com',
-  organization: "{YOUR_ORGANIZATION_ID_OR_NAME}"
-)
-
-universal_login_url = @auth0_client.authorization_url("https://{YOUR_APPLICATION_CALLBACK_URL}", {
-  organization: "{ORGANIZATION_QUERY_PARAM}", # You can override organization if needed
-  invitation: "{INVITATION_QUERY_PARAM}"
-})
-
-# redirect_to universal_login_url
-```
-
-## ID Token Validation
-
-An ID token may be present in the credentials received after authentication. This token contains information associated with the user that has just logged in, provided the scope used contained `openid`. You can [read more about ID tokens here](https://auth0.com/docs/tokens/concepts/id-tokens).
-
-Before accessing its contents, you must first validate the ID token to ensure it has not been tampered with and that it is meant for your application to consume. Use the `validate_id_token` method to do so:
-
-```ruby
-begin
-  @auth0_client.validate_id_token 'YOUR_ID_TOKEN'
-rescue Auth0::InvalidIdToken => e
-  # In this case the ID Token contents should not be trusted
-end
-```
-
-The method takes the following optional keyword parameters:
-
-| Parameter      | Type           | Description                                                                                                               | Default value                                                                                                          |
-| -------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `algorithm`    | `JWTAlgorithm` | The [signing algorithm](https://auth0.com/docs/tokens/concepts/signing-algorithms) used by your Auth0 application.        | `Auth0::Algorithm::RS256` (using the [JWKS URL](https://auth0.com/docs/tokens/concepts/jwks) of your **Auth0 Domain**) |
-| `leeway`       | Integer        | Number of seconds to account for clock skew when validating the `exp`, `iat` and `azp` claims.                            | `60`                                                                                                                   |
-| `nonce`        | String         | The `nonce` value you sent in the call to `/authorize`, if any.                                                           | `nil`                                                                                                                  |
-| `max_age`      | Integer        | The `max_age` value you sent in the call to `/authorize`, if any.                                                         | `nil`                                                                                                                  |
-| `issuer`       | String         | By default the `iss` claim will be checked against the URL of your **Auth0 Domain**. Use this parameter to override that. | `nil`                                                                                                                  |
-| `audience`     | String         | By default the `aud` claim will be compared to your **Auth0 Client ID**. Use this parameter to override that.             | `nil`                                                                                                                  |
-| `organization` | String         | By default the `org_id` or `org_name` claims will be compared to the `organization` value specified at client creation. Use this parameter to override that.          | `nil`                                                                                                                  |
-
-You can check the signing algorithm value under **Advanced Settings > OAuth > JsonWebToken Signature Algorithm** in your Auth0 application settings panel. [We recommend](https://auth0.com/docs/tokens/concepts/signing-algorithms#our-recommendation) that you make use of asymmetric signing algorithms like `RS256` instead of symmetric ones like `HS256`.
-
-```ruby
-# HS256
-
-begin
-  @auth0_client.validate_id_token 'YOUR_ID_TOKEN', algorithm: Auth0::Algorithm::HS256.secret('YOUR_SECRET')
-rescue Auth0::InvalidIdToken => e
-  # Handle error
-end
-
-# RS256 with a custom JWKS URL
-
-begin
-  @auth0_client.validate_id_token 'YOUR_ID_TOKEN', algorithm: Auth0::Algorithm::RS256.jwks_url('YOUR_URL')
-rescue Auth0::InvalidIdToken => e
-  # Handle error
-end
-```
-
-### Organization claim validation
-
-If an `org_id` or `org_name` claim is present in the access   token, then the claim should be validated by the API to ensure that the value received is expected or known.
-
-In particular:
-
-- The issuer (iss) claim should be checked to ensure the token was issued by Auth0
-
-- the `org_id` or `org_name` claim should be checked to ensure it is a value that is already known to the application. Which claim you check depends on the organization value being validated: if it starts with `org_`, validate against the `org_id` claim. Otherwise, validate against `org_name`. Further, the value of the `org_name` claim will always be lowercase. To aid the developer experience, you may also lowercase the input organization name when checking against the `org_name`, but do not modify the `org_name` claim value.
-
-This could be validated against a known list of organization IDs or names, or perhaps checked in conjunction with the current request URL. e.g. the sub-domain may hint at what organization should be used to validate the Access Token.
-
-Normally, validating the issuer would be enough to ensure that the token was issued by Auth0. In the case of organizations, additional checks should be made so that the organization within an Auth0 tenant is expected.
-
-If the claim cannot be validated, then the application should deem the token invalid.
-
-```ruby
-begin
-  @auth0_client.validate_id_token 'YOUR_ID_TOKEN', organization: '{Expected org_id or org_name}'
-rescue Auth0::InvalidIdToken => e
-  # In this case the ID Token contents should not be trusted
-end
-```
-
-For more information, please read [Work with Tokens and Organizations](https://auth0.com/docs/organizations/using-tokens) on Auth0 Docs.
-
-## Use a private key to authenticate with Auth0
-
-You are able to take advantage of using a JWT signed with a private key to authenticate with Auth0 in place of using a client secret.
-
-**Note:** you must upload the corresponding public key to your Auth0 tenant, so that Auth0 is able to verify the JWT signature.
-
-Specify the client assertion key when creating the Auth0 client as in the following example:
-
-```ruby
-key_string = File.read 'key.pem'
-key = OpenSSL::PKey::RSA.new key_string
-
-client = Auth0Client.new(
-  domain: 'AUTH0_DOMAIN',
-  client_id: 'AUTH0_CLIENT_ID',
-  client_assertion_signing_key: key,
-  client_assertion_signing_alg: 'RS256')
-```
-
-Some notes:
-
-* If both `client_secret` and `client_assertion_signing_key` are specified, `client_assertion_signing_key` takes precedence
-* `client_assertion_signing_alg` is optional and defaults to `RS256` if omitted
-* Only `RS256`, `RS384` and `PS256` algorithms are supported by Auth0 currently

data/Gemfile

@@ -1,18 +0,0 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in auth0.gemspec
-gemspec
-
-group :development do
-  gem 'terminal-notifier-guard', require: false unless ENV['CIRCLECI']
-  gem 'rubocop', require: false
-  gem 'rubocop-rails', require: false
-end
-
-group :test do
-  gem 'webmock', require: false
-  gem 'vcr', require: false
-  gem 'simplecov-cobertura'
-  gem 'timecop', require: false
-  gem 'pp'
-end