omniauth-rocketchat 0.1.3 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e6e734479555a66972b720b9d9c4843e322b28c04a7f0a928fddb6a6158ecaeb
-  data.tar.gz: 6a4de526dad4f5a0371cbce48a47a55d656164d330ed574e555b29d0eccdbbe7
+  metadata.gz: 577664c3ad65b560985c9c1453a5c9960ee791099bea6e6467800f3782b01f11
+  data.tar.gz: e67724922fe367825ecd219e9e35762e8d87dd6dce30ef1353a4c998586262f0
 SHA512:
-  metadata.gz: 7e2acd00131584a457a78cd16923d667416377555553f3e7343f9876fcd8abb77710bafa00a4b64f32ffc9c2d946ed2f0484f2f51fc282bfab26447e7f15f086
-  data.tar.gz: 34921d9fa071a2c2bd46381ac8aad98f802cf0bc4445f04920cd11e0a8200cff7487b9ea022f3be0f66e132f87f35cf4582b1de0265422cc34f99f7072da9cb2
+  metadata.gz: ba50d26c8218a998b8fcb89d2fb4d0c992f98abbfa7bfb7e054fc4118963f26f081b6081c514c76aa96ee0748764f159e1b9b439b6f40b175efd468baaa0825c
+  data.tar.gz: 00b20862f69167b033592c384e7bcdc68aeaee7cb1787a6783c5d5dfd195c1bbbc1f3aa905e4eab419d1c35c24317de79973f9a527d37ce93b011081d0ac14f6

data/CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+### Unreleased
+
+### 0.2.0 (2026-03-08)
+
+This release contains breaking changes. See [Upgrade Instructions](UPGRADE.md#version-02) for detailed upgrade instructions.
+
+#### Breaking
+
+- Bumps required Ruby version `>= 3.2`.
+- The `info` hash now returns the expected [Auth Hash Schema 1.0+](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema).
+- Always returns `info.email`, even if the email was not verified. Check `info.email_verified` for verification status.

data/CODE_OF_CONDUCT.md

@@ -1,132 +1,10 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
 
-## Our Pledge
+"omniauth-rocketchat" follows [The Ruby Community Conduct Guideline](https://www.ruby-lang.org/en/conduct) in all "collaborative space", which is defined as community communications channels (such as mailing lists, submitted patches, commit comments, etc.):
 
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
+* Participants will be tolerant of opposing views.
+* Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
+* When interpreting the words and actions of others, participants should always assume good intentions.
+* Behaviour which can be reasonably considered harassment will not be tolerated.
 
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-david.uhlig[‎ at ‎]gmail.com.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
+If you have any concerns about behaviour within this project, please contact us at ["david.uhlig@gmail.com"](mailto:"david.uhlig@gmail.com").

data/LICENSE.md

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 David Uhlig
+Copyright (c) 2024-present David Uhlig
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -1,14 +1,36 @@
-# OmniAuth Rocket Chat OAuth2 Strategy
+[Rocket Chat]: https://rocket.chat/
+[OmniAuth]: https://github.com/omniauth/omniauth
+[gem]: https://rubygems.org/gems/omniauth-rocketchat
+[license]: LICENSE.md
+[contributing]: CODE_OF_CONDUCT.md
+
+# 🔓 OmniAuth Rocket Chat
 
 [![Gem Version](http://img.shields.io/gem/v/omniauth-rocketchat.svg)][gem]
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)][license]
 [![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)][contributing]
 
-[gem]: https://rubygems.org/gems/omniauth-rocketchat
-[license]: LICENSE.md
-[contributing]: CODE_OF_CONDUCT.md
+## 🚀 Authenticate with Rocket Chat in your Ruby applications
+
+This unofficial [OmniAuth] strategy allows your application's users to authenticate with [Rocket Chat] as the identity provider (aka social login).
+
+## Requirements
 
-Unofficial OmniAuth strategy to authenticate with [Rocket Chat](https://rocket.chat/) through OAuth2 in [OmniAuth](https://github.com/omniauth/omniauth).
+* Ruby `>= 3.2.0`.
+* Rocket Chat `<= 7.4.0` (EOL) or `>= 8.0.0`. See [Compatibility](#compatibility) below.
+
+### Compatibility
+
+Rocket.Chat version 7.4.0 [introduced a bug](https://github.com/RocketChat/Rocket.Chat/issues/35419) that breaks third-party logins. A [partial fix](https://github.com/RocketChat/Rocket.Chat/pull/37707) is available starting in version 8.0.0, but PKCE flows remain affected. Until this is fully resolved, set `pkce: false` in the configurations below.
+
+#### Compatibility Matrix
+
+Excluding EOL versions:
+
+| Rocket Chat Version | `pkce: false`      | `pkce: true` |
+|---------------------|--------------------|--------------|
+| `>= 7.10.x`         | :x:                | :x:          |
+| `>= 8.0.x`          | :white_check_mark: | :x:          |
 
 ## Installation
 
@@ -20,80 +42,139 @@ gem 'omniauth-rocketchat'
 
 Then execute `bundle install`.
 
-## Rocket Chat Setup
+## Configuration
+
+> [!NOTE]
+> Rocket Chat doesn't support `scopes`. Users grant you full permissions to their account. Handle responsibly!
 
-You need to register your application with your Rocket Chat instance to obtain the `Client ID` and `Client Secret`. You will also need to add this applications host(s). This whitelists your application for the callback redirect. You can do this by following the steps below:
+### Rocket Chat
 
-* Go to your Rocket Chat instance and login as an administrator.
-* Go to `Administration` -> `Third-party login`.
-* Click on `New Application`.
-  * Check the `Active` checkbox.
-  * Fill in the `Application Name` and `Redirect URL`. The redirect URL for devise looks like `https://example.com/users/auth/rocketchat/callback`. You can add multiple hosts by separating them with a comma.
-  * Click on `Save`.
-* Select the third-party login you just created.
-  * Copy the `Client ID` and `Client Secret`.
+To enable third-party login, register your application in Rocket Chat to obtain the `Client ID` and `Client Secret`. Add your application's host(s) to whitelist callback redirects by following these steps:
 
-## Integration
+1. Log in to your Rocket Chat instance as an administrator.
+2. Navigate to Administration > Third-party login (e.g., https://example.com/admin/third-party-login).
+3. Click New Application:
+   * Enable the Active checkbox.
+   * Enter an Application Name and Redirect URL (e.g., https://example.com/users/auth/rocketchat/callback for Devise).
+   * Click Save.
+4. Select your new application and copy the `Client ID` and `Client Secret`.
 
-Pick one of the following methods to integrate the strategy with your application.
+### Ruby Integration
 
-### Basic Usage
+Choose one of the following methods to integrate the strategy with your Ruby application.
+
+#### Required Options
     
 ```ruby
 use OmniAuth::Builder do
-  provider :rocketchat,
-  ENV["ROCKETCHAT_CLIENT_ID"],
-  ENV["ROCKETCHAT_CLIENT_SECRET"],
-  client_options: {
-    site: "https://example.com"
-  }
+  provider(
+    :rocketchat, 
+    ENV["CLIENT_ID"],
+    ENV["CLIENT_SECRET"], 
+    pkce: false,
+    client_options: {
+      site: "https://example.com"
+    }
+  )
 end
 ```
 
-### With Custom Endpoints
+#### Custom Endpoints
+
+If you modified the endpoint URL's in Rocket Chat, set `authorize_url` and `token_url`.
+
 ```ruby
 use OmniAuth::Builder do
-  provider :rocketchat,
-  ENV["ROCKETCHAT_CLIENT_ID"],
-  ENV["ROCKETCHAT_CLIENT_SECRET"],
-  client_options: {
-    site: "https://example.com",
-    authorize_url: "/custom/oauth/authorize",
-    token_url: "/custom/oauth/token"
-  }
+  provider(
+    :rocketchat,
+    ENV["CLIENT_ID"],
+    ENV["CLIENT_SECRET"],
+    pkce: false,
+    client_options: {
+      site: "https://example.com",
+      authorize_url: "/custom/oauth/authorize",
+      token_url: "/custom/oauth/token"
+    }
+  )
 end
 ```
 
-### In Rails
+#### Custom Identifier
+
+Set the `name` option to distinguish between multiple Rocket Chat instances. It appears in the OmniAuth auth hash `request.env["omniauth.auth"]` under the `provider` key.
+
+```ruby
+use OmniAuth::Build do
+  provider(
+    :rocketchat,
+    ENV["CLIENT_ID"],
+    ENV["CLIENT_SECRET"],
+    name: :some_other_name,
+    pkce: false,           
+    client_options: {
+      site: "https://example.com"
+    }
+  )
+end
+```
+
+### Rails Integration
+
+Choose one of the following methods to integrate the strategy with your Ruby on Rails application. The [Custom Endpoints](#custom-endpoints) and [Identifier](#custom-identifier) options apply here as well.
+
+#### General
+
 ```ruby
 # config/initializers/rocketchat.rb
 Rails.application.config.middleware.use OmniAuth::Builder do
-  provider :rocketchat,
-  ENV["ROCKETCHAT_CLIENT_ID"],
-  ENV["ROCKETCHAT_CLIENT_SECRET"],
-  client_options: {
-    site: "https://example.com"
-  }
+  provider(
+    :rocketchat,
+    ENV["CLIENT_ID"],
+    ENV["CLIENT_SECRET"],
+    pkce: false,           
+    client_options: {
+      site: "https://example.com"
+    }
+  )
 end
 ```
 
-### With Devise
+#### When using Devise
+
+Use this integration if you use Devise with the `:omniauthable` module.
+
 ```ruby
 # config/initializers/rocketchat.rb
 Devise.setup do |config|
-  config.omniauth :rocketchat,
-  ENV["ROCKETCHAT_CLIENT_ID"],
-  ENV["ROCKETCHAT_CLIENT_SECRET"],
-  client_options: {
-    site: "https://example.com"
-  }
+  config.omniauth(
+    :rocketchat,
+    ENV["CLIENT_ID"],
+    ENV["CLIENT_SECRET"],
+    pkce: false,
+    client_options: {
+      site: "https://example.com"
+    }
+  )
 end
 ```
 
-## Configuration
+## Auth Hash Schema
+
+### User Info
+
+This strategy returns information about the authenticated user in the [Auth Hash Schema 1.0+](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema). The following information is available in the `info` hash:
+
+* `name`: The user's full name.
+* `nickname`: The user's Rocket Chat username.
+* `email`: The user's email address. The strategy prioritizes verified email addresses but will fall back to the first available one if no verified address is found.
+* `email_verified`: A boolean indicating whether the email address has been verified on the Rocket Chat instance.
+* `image`: The URL to the user's avatar.
+
+You can find the complete profile information returned by Rocket Chat in `extra.raw_info`.
+
+### Credentials
 
-* The `client_options` options: `authorize_url` and `token_url` are optional and default to `/oauth/authorize` and `/oauth/token` respectively.
-* `scope` has no effect on Rocket Chat. Users grant you full permissions to their account. Handle responsibly!
+Rocket Chat also returns access and refresh tokens along with other information in the `credentials` hash.
 
 ## Versioning
 
@@ -107,5 +188,5 @@ Bug reports and pull requests are welcome on the [GitHub project page](https://g
 
 ## License
 
-Copyright &copy; 2024-2025 David Uhlig. See [LICENSE][] for details.
+Copyright &copy; 2024-2026 David Uhlig. See [LICENSE][] for details.
 

data/Rakefile

@@ -1,19 +1,10 @@
-#!/usr/bin/env rake
+# frozen_string_literal: true
 
 require "bundler/gem_tasks"
 require "rspec/core/rake_task"
 
-RSpec::Core::RakeTask.new
+RSpec::Core::RakeTask.new(:spec)
 
-task test: :spec
+require "standard/rake"
 
-begin
-  require "rubocop/rake_task"
-  RuboCop::RakeTask.new
-rescue LoadError
-  task :rubocop do
-    $stderr.puts "RuboCop is disabled"
-  end
-end
-
-task default: %i[spec rubocop]
+task default: %i[spec standard]

data/UPGRADE.md

@@ -0,0 +1,34 @@
+# OmniAuth Rocket Chat Upgrade Guide
+
+Follow this guide to upgrade your OmniAuth Rocket Chat Strategy to the next version
+
+## Version 0.2.x
+
+This version introduces breaking changes that may require your attention.
+
+### Ruby version requirement
+
+The minimum required Ruby version is now **3.2.0**. Support for older versions has been dropped.
+
+### OmniAuth Auth Hash Schema 1.0+ compliance
+
+The `info` hash has been refactored to follow the [Auth Hash Schema 1.0+](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema).
+
+*   `nickname` replaces `username`.
+*   `image` (the avatar URL) replaces the nested `avatar` hash.
+*   `active` and `roles` have been removed.
+
+If you still need access to `active` or `roles`, you can find them in `extra.raw_info`.
+
+### Email handling
+
+The strategy now always returns an `info.email` address, even if it hasn't been verified on the Rocket Chat instance.
+
+*   A new boolean field `info.email_verified` indicates the verification status.
+*   The strategy prioritizes verified email addresses but will fall back to the first available one.
+
+### PKCE requirement
+
+Rocket.Chat version 7.4.0 [introduced a bug](https://github.com/RocketChat/Rocket.Chat/issues/35419) that breaks third-party logins. A [partial fix](https://github.com/RocketChat/Rocket.Chat/pull/37707) is available starting in version 8.0.0, but PKCE flows remain affected.
+
+Until this is fully resolved, you must set `pkce: false` in your configuration.

data/lib/omniauth/strategies/rocketchat.rb

@@ -56,6 +56,9 @@ module OmniAuth
     #                     }
     #   end
     class RocketChat < OmniAuth::Strategies::OAuth2
+      # Returns profile information about the authenticated user.
+      # @see https://developer.rocket.chat/apidocs/get-profile-information
+      PROFILE_INFO_ENDPOINT = "/api/v1/me"
       DEFAULT_AUTHORIZE_URL = "/oauth/authorize"
       DEFAULT_TOKEN_URL = "/oauth/token"
 
@@ -71,46 +74,48 @@ module OmniAuth
       option :pkce, true
 
       uid do
-        raw_info["_id"]
+        profile["_id"]
       end
 
-      # Most commonly used info from the +/api/v1/me+ endpoint.
+      # User info from the +/api/v1/me+ endpoint according to the OmniAuth Auth Hash.
       #
-      # +info.email+ returns +nil+ if the user has no confirmed email address.
-      # If email confirmation is disabled on the Rocket Chat instance, the email
-      # will never be confirmed.
+      # Note: If email confirmation is disabled on the Rocket Chat instance,
+      # the email will never be confirmed, i.e. `email_verified` will always be `false`.
       #
       # You may want to handle the +extra.raw_info.emails+ array in this case.
-      # It contains all email addresses associated with the user. Confirmed and
-      # unconfirmed.
+      # It contains all email addresses associated with the user. Verified and unverified.
       info do
         {
-          email: raw_info["email"],
-          active: raw_info["active"],
-          roles: raw_info["roles"],
-          name: raw_info["name"],
-          username: raw_info["username"],
-          avatar: {
-            url: raw_info["avatar_url"],
-            e_tag: raw_info["avatar_e_tag"],
-            origin: raw_info["avatar_origin"]
-          }
+          name: profile["name"],
+          email: email["address"],
+          email_verified: email["verified"],
+          nickname: profile["username"],
+          image: profile["avatar_url"]
         }
       end
 
       extra do
         {
-          raw_info: raw_info
+          raw_info: profile
         }
       end
 
-      def raw_info
-        @raw_info ||= access_token.get("/api/v1/me").parsed
-      end
-
       def callback_url
         full_host + callback_path
       end
+
+      private
+
+      def profile
+        @profile ||= access_token.get(PROFILE_INFO_ENDPOINT).parsed
+      end
+
+      def email
+        @email ||=
+          profile["emails"].find { |email| email["verified"] } ||
+          profile["emails"].first ||
+          {"address" => nil, "verified" => false}
+      end
     end
   end
 end

data/lib/omniauth-rocketchat/version.rb

@@ -2,6 +2,6 @@
 
 module OmniAuth
   module RocketChat
-    VERSION = "0.1.3"
+    VERSION = "0.2.0"
   end
 end

metadata

@@ -1,42 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-rocketchat
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.2.0
 platform: ruby
 authors:
 - David Uhlig
-bindir: bin
+autorequire:
+bindir: exe
 cert_chain: []
-date: 2025-01-16 00:00:00.000000000 Z
+date: 2026-03-08 00:00:00.000000000 Z
 dependencies:
-- !ruby/object:Gem::Dependency
-  name: oauth2
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
-- !ruby/object:Gem::Dependency
-  name: omniauth
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: omniauth-oauth2
   requirement: !ruby/object:Gem::Requirement
@@ -52,127 +25,103 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '1.8'
 - !ruby/object:Gem::Dependency
-  name: rake
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '13.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '13.0'
-- !ruby/object:Gem::Dependency
-  name: rubocop
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.70'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.70'
-- !ruby/object:Gem::Dependency
-  name: rubocop-performance
+  name: irb
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.23'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.23'
+        version: '0'
 - !ruby/object:Gem::Dependency
-  name: rubocop-rspec
+  name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '13.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '13.0'
 - !ruby/object:Gem::Dependency
-  name: rubocop-rails-omakase
+  name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '3.2'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '3.2'
 - !ruby/object:Gem::Dependency
-  name: rspec
+  name: standard
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.8'
+        version: '1.3'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.8'
+        version: '1.3'
 - !ruby/object:Gem::Dependency
   name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0.16'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0.16'
-description: Allows your application to integrate with Rocket Chat through their "Third-party
-  login" feature.
-email: david.uhlig@gmail.com
+        version: '0'
+description: 'Allows your application to integrate with Rocket Chat through their
+  "Third-party login" feature.
+
+  '
+email:
+- david.uhlig@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".gitignore"
 - ".rubocop.yml"
+- CHANGELOG.md
 - CODE_OF_CONDUCT.md
-- Gemfile
 - LICENSE.md
 - README.md
 - Rakefile
+- UPGRADE.md
 - lib/omniauth-rocketchat.rb
 - lib/omniauth-rocketchat/version.rb
 - lib/omniauth/strategies/rocketchat.rb
-- omniauth-rocketchat.gemspec
 homepage: https://github.com/david-uhlig/omniauth-rocketchat
 licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/david-uhlig/omniauth-rocketchat
   source_code_uri: https://github.com/david-uhlig/omniauth-rocketchat
+  changelog_uri: https://github.com/david-uhlig/omniauth-rocketchat/blob/main/CHANGELOG.md
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -180,14 +129,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.2'
+      version: 3.2.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.5
+      version: '0'
 requirements: []
-rubygems_version: 3.6.1
+rubygems_version: 3.4.19
+signing_key:
 specification_version: 4
 summary: An unofficial Rocket Chat OAuth2 strategy.
 test_files: []

data/.gitignore

@@ -1,56 +0,0 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/spec/reports/
-/spec/examples.txt
-/test/tmp/
-/test/version_tmp/
-/tmp/
-
-# Used by dotenv library to load environment variables.
-# .env
-
-# Ignore Byebug command history file.
-.byebug_history
-
-## Specific to RubyMotion:
-.dat*
-.repl_history
-build/
-*.bridgesupport
-build-iPhoneOS/
-build-iPhoneSimulator/
-
-## Specific to RubyMotion (use of CocoaPods):
-#
-# We recommend against adding the Pods directory to your .gitignore. However
-# you should judge for yourself, the pros and cons are mentioned at:
-# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
-#
-# vendor/Pods/
-
-## Documentation cache and generated files:
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
-
-## Environment normalization:
-/.bundle/
-/vendor/bundle
-/lib/bundler/man/
-
-# for a library or gem, you might want to ignore these files since the code is
-# intended to run in multiple environments; otherwise, check them in:
-Gemfile.lock
-.ruby-version
-.ruby-gemset
-
-# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
-.rvmrc
-
-# Used by RuboCop. Remote config files pulled in from inherit_from directive.
-.rubocop-https?--*

data/Gemfile

@@ -1,22 +0,0 @@
-source "https://rubygems.org"
-
-ruby "3.3.6", platforms: [ :ruby, :x86_64_linux ]
-
-gem "rake", "~> 13.0"
-
-group :test do
-  gem "addressable", "~> 2.3.8", platforms: %i[jruby ruby_18]
-  gem "coveralls_reborn", "~> 0.28.0", require: false
-  gem "json", platforms: %i[jruby ruby_18 ruby_19]
-  gem "mime-types", "~> 3.6", platforms: %i[jruby ruby_18]
-  gem "rack-test"
-  gem "rest-client", "~> 2.1.0", platforms: %i[jruby ruby_18]
-  gem "rspec", "~> 3.8"
-  gem "rubocop", "~> 1.70", platforms: %i[ruby_19 ruby_20 ruby_21 ruby_22 ruby_23 ruby_24]
-  gem "simplecov-lcov"
-  gem "tins", "~> 1.13", platforms: %i[jruby_18 jruby_19 ruby_19]
-  gem "webmock", "~> 3.0"
-end
-
-# Specify your gem's dependencies in omniauth-oauth2.gemspec
-gemspec

data/omniauth-rocketchat.gemspec

@@ -1,43 +0,0 @@
-# frozen_string_literal: true
-
-require File.expand_path(
-  File.join("..", "lib", "omniauth-rocketchat", "version"),
-  __FILE__
-)
-
-Gem::Specification.new do |gem|
-  gem.name          = "omniauth-rocketchat"
-  gem.version       = OmniAuth::RocketChat::VERSION
-  gem.license       = "MIT"
-  gem.summary       = "An unofficial Rocket Chat OAuth2 strategy."
-  gem.description   = 'Allows your application to integrate with Rocket Chat through their "Third-party login" feature.'
-
-  gem.authors       = [ "David Uhlig" ]
-  gem.email         = "david.uhlig@gmail.com"
-  gem.homepage      = "https://github.com/david-uhlig/omniauth-rocketchat"
-
-  gem.metadata      = {
-    "homepage_uri" => gem.homepage,
-    "source_code_uri" => gem.homepage
-  }
-
-  gem.files         = `git ls-files -z`.split("\x0").reject { |f| f.start_with?('spec/') }
-  gem.require_paths = %w[lib]
-
-  gem.required_rubygems_version = '>= 1.3.5'
-  gem.required_ruby_version     = '>= 2.2'
-
-  gem.add_runtime_dependency 'oauth2', '~> 2.0'
-  gem.add_runtime_dependency 'omniauth', '~> 2.0'
-  gem.add_runtime_dependency 'omniauth-oauth2', '~> 1.8'
-
-  gem.add_development_dependency "rake", "~> 13.0"
-  gem.add_development_dependency "rubocop", "~> 1.70"
-  gem.add_development_dependency "rubocop-performance", "~> 1.23"
-  gem.add_development_dependency "rubocop-rspec", "~> 2.0"
-  gem.add_development_dependency "rubocop-rails-omakase", "~> 1.0"
-  gem.add_development_dependency "rspec", "~> 3.8"
-  gem.add_development_dependency "simplecov", "~> 0.16"
-
-  gem.platform = Gem::Platform::RUBY
-end