Skip to content

Vendor omniauth-cas3 gem

Jessie Young requested to merge jy-vendor-omniauth-cas into master

What does this MR do and why?

  • Our ultimate goal is to upgrade omniauth to v2.0. See the related issue
  • In order to upgrade omniauth to v2.0, we need to upgrade omniauth-cas3 because the latter has a dependency on the former.
  • There is an open issue asking the maintainer to make omniauth-cas3 compatible with omniauth v2.0 but it has not been responded to: https://github.com/tduehr/omniauth-cas3/issues/5
  • This MR vendors the gem and updates its .gemspec file so that it is compatible with omniauth v2.0
  • We may deprecate our usage of this gem in the future (issue)
  • MR where we vendored a different omniauth gem for same reasons: !92485 (merged)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Jessie Young

Merge request reports