edc8d0390e
Gitlab requires net-http 0.4.1: Because faraday >= 2, < 2.5 could not be found in locally installed gems and faraday >= 2.5, < 2.12.1 could not be found in locally installed gems, faraday >= 2, < 2.12.1 cannot be used. And because faraday >= 2.12.1 depends on faraday-net_http >= 2.0, < 3.5, faraday >= 2 requires faraday-net_http >= 2.0, < 3.5. Because faraday-net_http >= 3.4.0 depends on net-http >= 0.5.0 and faraday-net_http >= 2.0, < 3.4.0 could not be found in locally installed gems, faraday-net_http >= 2.0 requires net-http >= 0.5.0. Thus, faraday >= 2 requires net-http >= 0.5.0. So, because Gemfile depends on faraday ~> 2 and Gemfile depends on net-http = 0.4.1, version solving has failed. While fixing the problem, moved gitlab used packages to own package names with a PKGNAMESUFFIX of `-gitlab`. This should make the gitlab package much more stable if updates in the ports are done.
17 lines
924 B
Plaintext
17 lines
924 B
Plaintext
omniauth-oauth2-generic provides an OmniAuth strategy for authenticating with an
|
|
OAuth2 service using the authorization grant flow.
|
|
|
|
Most OmniAuth gems are written either as abstractions (omniauth-oauth2) or for a
|
|
specific provider (omniauth-github), but this one is designed to be configurable
|
|
enough to work with any basic OAuth2 provider. The primary differences between
|
|
OAuth2 provider strategies in OmniAuth are:
|
|
- The server's domain
|
|
- The URL paths used to authorize, request tokens and get user info
|
|
- The structure of the returned user information
|
|
|
|
These are all configurable options in this gem. There my be certain
|
|
requirements/features of some providers not covered by this gem's options, but
|
|
it was designed primarily so that if you are implementing your own OAuth2
|
|
provider for your service, you don't need to write an OmniAuth strategy as long
|
|
as it is compatible with the basic options provided by this gem.
|