omniauth-openid 2.0.1 → 2.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (29) hide show
  1. checksums.yaml +4 -4
  2. checksums.yaml.gz.sig +0 -0
  3. data/CHANGELOG.md +55 -0
  4. data/CODE_OF_CONDUCT.md +135 -0
  5. data/CONTRIBUTING.md +132 -0
  6. data/LICENSE.txt +23 -0
  7. data/README.md +420 -23
  8. data/SECURITY.md +42 -0
  9. data/lib/omniauth/openid/version.rb +8 -0
  10. data/lib/omniauth/strategies/open_id.rb +73 -46
  11. data/lib/omniauth-openid/version.rb +16 -3
  12. data/lib/omniauth-openid.rb +14 -2
  13. data.tar.gz.sig +4 -0
  14. metadata +229 -44
  15. metadata.gz.sig +0 -0
  16. data/.gemtest +0 -0
  17. data/.gitignore +0 -18
  18. data/.rspec +0 -2
  19. data/.travis.yml +0 -23
  20. data/.yardopts +0 -4
  21. data/Gemfile +0 -23
  22. data/Gemfile.lock +0 -88
  23. data/Guardfile +0 -9
  24. data/LICENSE +0 -19
  25. data/Rakefile +0 -6
  26. data/examples/sinatra.rb +0 -28
  27. data/omniauth-openid.gemspec +0 -20
  28. data/spec/omniauth/strategies/open_id_spec.rb +0 -90
  29. data/spec/spec_helper.rb +0 -17
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 13be670416c096d0ac1f7a7f5248d5b58e806b3b69883eafafc25ed83c230ee5
4
- data.tar.gz: a3b59e5573339f46695c9e8ed92858f5d9e3f5990c646299f7989d95afbd8791
3
+ metadata.gz: 15f84d82d9102e90ab73582c36048a7cd376d6f75851dca9bf3c08f83a9bd3f2
4
+ data.tar.gz: 37654826a5526a0e8326f81f477fd7efe2cb6e9bbc5309e6b850812b76b6caba
5
5
  SHA512:
6
- metadata.gz: e92d418d26125e3522d4c122e940502795b0cbf73940dfa4d2c8c6deae37b5c7fff95f3c88f4589cf1328041e9524ff4acdb355f15e2b008aec8c0e2ed30c248
7
- data.tar.gz: 8a23a7180d5a08a8ede236d7ab92d5471b23e4940250e4094f83be6c72388ee46e5b3728831d115cac762637711589756e7477a7402a136ae004532205e63c74
6
+ metadata.gz: 6f7033d1490194a8253639347723b424fd50653d28662c7c1769750e3b3de9b4db02d04a9553a52b5afc776319627372d590fc65722000965db121a92d2895a9
7
+ data.tar.gz: 494f27e8c30c5dc8f4ca40cb55ff27dcd2a419496e47bf3f54ebacbf93e7ed3a29c62dbe0258501ae6f79dd8890f9ca00d1d473e50f4b50d7e0a02de09519868
checksums.yaml.gz.sig ADDED
Binary file
data/CHANGELOG.md ADDED
@@ -0,0 +1,55 @@
1
+ # Changelog
2
+
3
+ This file documents all notable changes to this project since v2.0.2.
4
+
5
+ The format is based on [Keep a Changelog v1](https://keepachangelog.com/en/1.0.0/),
6
+ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.0.0.html).
7
+
8
+ ## [Unreleased]
9
+ ### Added
10
+ ### Changed
11
+ ### Deprecated
12
+ ### Removed
13
+ ### Fixed
14
+ ### Security
15
+
16
+ ## [2.0.2] - 2025-06-08
17
+ - TAG: [v2.0.2][2.0.2t]
18
+ - COVERAGE: 92.06% -- 348/378 lines in 15 files
19
+ - BRANCH COVERAGE: 79.49% -- 62/78 branches in 15 files
20
+ - 44.44% documented
21
+ ### Added
22
+ - Github Actions for Continuous Integration by @pboling
23
+ - Test workflows with latest dependencies and more platform and dep HEADs
24
+ - Expanded test suite, covering many more points of the dependency matrix
25
+ - More documentation by @pboling, @Aboling0
26
+ - 20 year signing cert expires 2045-04-29 by @pboling
27
+ - Added CITATION.cff by @pboling
28
+ - devcontainer for easier maintenance by @pboling
29
+ - Add SECURITY.md policy by @pboling
30
+ - CONTRIBUTING.md - Instructions for contributing by @pboling
31
+ - Modernized gem structure, and updated dependencies for development by @pboling
32
+ - Set `SKIP_GEM_SIGNING` in env to allow `gem build` without cryptographic signing requirement by @pboling
33
+ - Useful for linux distros whose package managers sign packages independently
34
+ - Example client / server in `/examples` by @pboling
35
+ ### Changed
36
+ - Updated Code of Conduct to Contributor Covenant v2.1 by @pboling
37
+
38
+ ## [2.0.1] - 2021-01-19
39
+ - TAG: [v2.0.0][2.0.0t]
40
+
41
+ ## [1.0.1] - 2011-11-04
42
+ - TAG: [v1.0.1][1.0.1t]
43
+
44
+ ## [1.0.0] - 2011-11-02
45
+ - TAG: [v1.0.][1.0.0t]
46
+
47
+ [Unreleased]: https://github.com/omniauth/omniauth-openid/compare/v2.0.2...HEAD
48
+ [2.0.2]: https://github.com/omniauth/omniauth-openid/compare/v2.0.2...v2.0.1
49
+ [2.0.2t]: https://github.com/omniauth/omniauth-openid/tags/v2.0.2
50
+ [2.0.1]: https://github.com/omniauth/omniauth-openid/compare/v2.0.1...v1.0.1
51
+ [2.0.1t]: https://github.com/omniauth/omniauth-openid/tags/v2.0.1
52
+ [1.0.1]: https://github.com/omniauth/omniauth-openid/compare/v1.0.1...v1.0.0
53
+ [1.0.1t]: https://github.com/omniauth/omniauth-openid/tags/v1.0.1
54
+ [1.0.0]: https://github.com/omniauth/omniauth-openid/compare/6019f3abd7b707567e2217c91be64f7a6c4aa34b...v1.0.0
55
+ [1.0.0t]: https://github.com/omniauth/omniauth-openid/tags/v1.0.0
data/CODE_OF_CONDUCT.md ADDED
@@ -0,0 +1,135 @@
1
+
2
+ # Contributor Covenant Code of Conduct
3
+
4
+ ## Our Pledge
5
+
6
+ We as members, contributors, and leaders pledge to make participation in our
7
+ community a harassment-free experience for everyone, regardless of age, body
8
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
9
+ identity and expression, level of experience, education, socio-economic status,
10
+ nationality, personal appearance, race, caste, color, religion, or sexual
11
+ identity and orientation.
12
+
13
+ We pledge to act and interact in ways that contribute to an open, welcoming,
14
+ diverse, inclusive, and healthy community.
15
+
16
+ ## Our Standards
17
+
18
+ Examples of behavior that contributes to a positive environment for our
19
+ community include:
20
+
21
+ * Demonstrating empathy and kindness toward other people
22
+ * Being respectful of differing opinions, viewpoints, and experiences
23
+ * Giving and gracefully accepting constructive feedback
24
+ * Accepting responsibility and apologizing to those affected by our mistakes,
25
+ and learning from the experience
26
+ * Focusing on what is best not just for us as individuals, but for the overall
27
+ community
28
+
29
+ Examples of unacceptable behavior include:
30
+
31
+ * The use of sexualized language or imagery, and sexual attention or advances of
32
+ any kind
33
+ * Trolling, insulting or derogatory comments, and personal or political attacks
34
+ * Public or private harassment
35
+ * Publishing others' private information, such as a physical or email address,
36
+ without their explicit permission
37
+ * Other conduct which could reasonably be considered inappropriate in a
38
+ professional setting
39
+
40
+ ## Enforcement Responsibilities
41
+
42
+ Community leaders are responsible for clarifying and enforcing our standards of
43
+ acceptable behavior and will take appropriate and fair corrective action in
44
+ response to any behavior that they deem inappropriate, threatening, offensive,
45
+ or harmful.
46
+
47
+ Community leaders have the right and responsibility to remove, edit, or reject
48
+ comments, commits, code, wiki edits, issues, and other contributions that are
49
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
50
+ decisions when appropriate.
51
+
52
+ ## Scope
53
+
54
+ This Code of Conduct applies within all community spaces, and also applies when
55
+ an individual is officially representing the community in public spaces.
56
+ Examples of representing our community include using an official email address,
57
+ posting via an official social media account, or acting as an appointed
58
+ representative at an online or offline event.
59
+
60
+ ## Enforcement
61
+
62
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
63
+ reported to the community leaders responsible for enforcement at
64
+ [![Contact BDFL][🚂bdfl-contact-img]][🚂bdfl-contact].
65
+ All complaints will be reviewed and investigated promptly and fairly.
66
+
67
+ All community leaders are obligated to respect the privacy and security of the
68
+ reporter of any incident.
69
+
70
+ ## Enforcement Guidelines
71
+
72
+ Community leaders will follow these Community Impact Guidelines in determining
73
+ the consequences for any action they deem in violation of this Code of Conduct:
74
+
75
+ ### 1. Correction
76
+
77
+ **Community Impact**: Use of inappropriate language or other behavior deemed
78
+ unprofessional or unwelcome in the community.
79
+
80
+ **Consequence**: A private, written warning from community leaders, providing
81
+ clarity around the nature of the violation and an explanation of why the
82
+ behavior was inappropriate. A public apology may be requested.
83
+
84
+ ### 2. Warning
85
+
86
+ **Community Impact**: A violation through a single incident or series of
87
+ actions.
88
+
89
+ **Consequence**: A warning with consequences for continued behavior. No
90
+ interaction with the people involved, including unsolicited interaction with
91
+ those enforcing the Code of Conduct, for a specified period of time. This
92
+ includes avoiding interactions in community spaces as well as external channels
93
+ like social media. Violating these terms may lead to a temporary or permanent
94
+ ban.
95
+
96
+ ### 3. Temporary Ban
97
+
98
+ **Community Impact**: A serious violation of community standards, including
99
+ sustained inappropriate behavior.
100
+
101
+ **Consequence**: A temporary ban from any sort of interaction or public
102
+ communication with the community for a specified period of time. No public or
103
+ private interaction with the people involved, including unsolicited interaction
104
+ with those enforcing the Code of Conduct, is allowed during this period.
105
+ Violating these terms may lead to a permanent ban.
106
+
107
+ ### 4. Permanent Ban
108
+
109
+ **Community Impact**: Demonstrating a pattern of violation of community
110
+ standards, including sustained inappropriate behavior, harassment of an
111
+ individual, or aggression toward or disparagement of classes of individuals.
112
+
113
+ **Consequence**: A permanent ban from any sort of public interaction within the
114
+ community.
115
+
116
+ ## Attribution
117
+
118
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119
+ version 2.1, available at
120
+ [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121
+
122
+ Community Impact Guidelines were inspired by
123
+ [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124
+
125
+ For answers to common questions about this code of conduct, see the FAQ at
126
+ [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127
+ [https://www.contributor-covenant.org/translations][translations].
128
+
129
+ [homepage]: https://www.contributor-covenant.org
130
+ [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131
+ [Mozilla CoC]: https://github.com/mozilla/diversity
132
+ [FAQ]: https://www.contributor-covenant.org/faq
133
+ [translations]: https://www.contributor-covenant.org/translations
134
+ [🚂bdfl-contact]: http://www.railsbling.com/contact
135
+ [🚂bdfl-contact-img]: https://img.shields.io/badge/Contact-BDFL-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,132 @@
1
+ # Contributing
2
+
3
+ Bug reports and pull requests are welcome on GitHub at [https://github.com/omniauth/omniauth-openid][🚎src-main].
4
+ This project should be a safe, welcoming space for collaboration, so contributors agree to adhere to
5
+ the [code of conduct][🤝conduct].
6
+
7
+ To submit a patch, please fork the project, create a patch with tests, and send a pull request.
8
+
9
+ Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog].
10
+
11
+ ## Help out!
12
+
13
+ Take a look at the `reek` list which is the file called `REEK` and find something to improve.
14
+
15
+ Follow these instructions:
16
+
17
+ 1. Fork the repository
18
+ 2. Create a feature branch (`git checkout -b my-new-feature`)
19
+ 3. Make some fixes.
20
+ 4. Commit changes (`git commit -am 'Added some feature'`)
21
+ 5. Push to the branch (`git push origin my-new-feature`)
22
+ 6. Make sure to add tests for it. This is important, so it doesn't break in a future release.
23
+ 7. Create new Pull Request.
24
+
25
+ ## Appraisals
26
+
27
+ From time to time the appraisal gemfiles in `gemfiles/` will need to be updated.
28
+
29
+ NOTE: The `eval_gemfile` feature comes from a [fork][🚎appraisal-fork] of Appraisal.
30
+
31
+ Please upvote the PR for `eval_gemfile` [support][🚎appraisal-eval-gemfile-pr]
32
+
33
+ Create or update them with the commands:
34
+
35
+ ```shell
36
+ BUNDLE_GEMFILE=Appraisal.root.gemfile bundle
37
+ BUNDLE_GEMFILE=Appraisal.root.gemfile bundle exec appraisal update
38
+ bundle exec rake rubocop_gradual:autocorrect
39
+ ```
40
+
41
+ When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
42
+
43
+ ## The Reek List
44
+
45
+ Take a look at the `reek` list which is the file called `REEK` and find something to improve.
46
+
47
+ To refresh the `reek` list:
48
+
49
+ ```bash
50
+ bundle exec reek > REEK
51
+ ```
52
+
53
+ ## Run Tests
54
+
55
+ To run all tests:
56
+
57
+ ```bash
58
+ bundle exec rake test
59
+ ```
60
+
61
+ ## Lint It
62
+
63
+ Run all the default tasks, which includes running the gradually autocorrecting linter, `rubocop-gradual`.
64
+
65
+ ```bash
66
+ bundle exec rake
67
+ ```
68
+
69
+ Or just run the linter.
70
+
71
+ ```bash
72
+ bundle exec rake rubocop_gradual:autocorrect
73
+ ```
74
+
75
+ ## Contributors
76
+
77
+ [![Contributors][🖐contributors-img]][🖐contributors]
78
+
79
+ Made with [contributors-img][🖐contrib-rocks].
80
+
81
+ ## For Maintainers
82
+
83
+ ### One-time, Per-maintainer, Setup
84
+
85
+ **IMPORTANT**: To sign a build,
86
+ a public key for signing gems will need to be picked up by the line in the
87
+ `gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there).
88
+ All releases to RubyGems.org are signed releases.
89
+ See: [RubyGems Security Guide][🔒️rubygems-security-guide]
90
+
91
+ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in the environment.
92
+
93
+ ### To release a new version:
94
+
95
+ 1. Run `bin/setup && bin/rake` as a "test, coverage, & linting" sanity check
96
+ 2. Update the version number in `version.rb`, and ensure `CHANGELOG.md` reflects changes
97
+ 3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
98
+ 4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
99
+ 5. Run `git push` to trigger the final CI pipeline before release, and merge PRs
100
+ - NOTE: Remember to [check the build][🧪build].
101
+ 6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
102
+ 7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
103
+ 8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
104
+ 9. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
105
+ - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
106
+ - If the echo above has no output, then it didn't work.
107
+ - Note: `zsh/datetime` module is needed, if running `zsh`.
108
+ - In older versions of `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
109
+ 10. Run `bundle exec rake build`
110
+ 11. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
111
+ to create SHA-256 and SHA-512 checksums. This functionality is provided by the `stone_checksums`
112
+ [gem][💎stone_checksums].
113
+ - The script automatically commits but does not push the checksums
114
+ 12. Run `bundle exec rake release` which will create a git tag for the version,
115
+ push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
116
+
117
+ 13. [🚎src-main]: https://github.com/omniauth/omniauth-openid
118
+ [🧪build]: https://github.com/omniauth/omniauth-openid/actions
119
+ [🤝conduct]: https://github.com/omniauth/omniauth-openid/blob/master/CODE_OF_CONDUCT.md
120
+ [🖐contrib-rocks]: https://contrib.rocks
121
+ [🖐contributors]: https://github.com/omniauth/omniauth-openid/graphs/contributors
122
+ [🖐contributors-img]: https://contrib.rocks/image?repo=omniauth/omniauth-openid
123
+ [💎rubygems]: https://rubygems.org
124
+ [🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
125
+ [🔒️rubygems-checksums-pr]: https://github.com/rubygems/rubygems/pull/6022
126
+ [🔒️rubygems-guides-pr]: https://github.com/rubygems/guides/pull/325
127
+ [💎stone_checksums]: https://github.com/pboling/stone_checksums
128
+ [📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
129
+ [📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
130
+ [🚎appraisal-eval-gemfile-pr]: https://github.com/thoughtbot/appraisal/pull/248
131
+ [🚎appraisal-fork]: https://github.com/pboling/appraisal/tree/galtzo
132
+ [🏃‍♂️runner-tool-cache]: https://github.com/ruby/ruby-builder/releases/tag/toolcache
data/LICENSE.txt ADDED
@@ -0,0 +1,23 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2025 Peter H. Boling, and omniauth-openid contributors
4
+ Copyright (c) 2010-2011 Michael Bleigh, and Intridea, Inc.
5
+
6
+ Permission is hereby granted, free of charge, to any person obtaining
7
+ a copy of this software and associated documentation files (the
8
+ "Software"), to deal in the Software without restriction, including
9
+ without limitation the rights to use, copy, modify, merge, publish,
10
+ distribute, sublicense, and/or sell copies of the Software, and to
11
+ permit persons to whom the Software is furnished to do so, subject to
12
+ the following conditions:
13
+
14
+ The above copyright notice and this permission notice shall be
15
+ included in all copies or substantial portions of the Software.
16
+
17
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
18
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
19
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
20
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
21
+ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
22
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
23
+ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.