Project
Reverse Dependencies for omniauth
The projects listed here declare omniauth as a runtime or development dependency
0.0
Using OAuth 1.0
2021
2022
2023
2024
2025
2026
0.0
OmniAuth strategy for the SurveyMonkey developer API
2021
2022
2023
2024
2025
2026
0.0
Survemonkey OAuth2 strategy for OmniAuth 1.0
2021
2022
2023
2024
2025
2026
0.0
OmniAuth strategy for SUZURI
2021
2022
2023
2024
2025
2026
0.0
OmniAuth strategy for Swedbank Banklink
2021
2022
2023
2024
2025
2026
0.0
Official OmniAuth strategies for synced.
2021
2022
2023
2024
2025
2026
0.0
Ensures local user records are created or updated with the latest data from the SSO provider after a successful OmniAuth login.
2021
2022
2023
2024
2025
2026
0.0
an omniauth strategy for 163 weibo
2021
2022
2023
2024
2025
2026
0.0
OmniAuth strategy for Tanita Health Planet
2021
2022
2023
2024
2025
2026
0.0
This is the strategy for authenticating to your Tanmer service
2021
2022
2023
2024
2025
2026
0.0
an omniauth strategy for taobao
2021
2022
2023
2024
2025
2026
0.0
An omniauth provider to connect to Tapjoy
2021
2022
2023
2024
2025
2026
0.0
OmniAuth strategy for Treasure Data
2021
2022
2023
2024
2025
2026
0.0
A TD Ameritrade OAuth2 strategy for OmniAuth 1.x. This allows you to login to TD Ameritrade with your ruby app.
2021
2022
2023
2024
2025
2026
0.0
OAuth2 strategy to use with Teamleader API
2021
2022
2023
2024
2025
2026
0.0
Official OmniAuth strategy for TeamSnap
2021
2022
2023
2024
2025
2026
0.0
Authenticate with Telegram using Telepass
2021
2022
2023
2024
2025
2026
0.0
Omniauth Strategy for Tent
2021
2022
2023
2024
2025
2026
0.0
Tenzing strategy for OmniAuth.
2021
2022
2023
2024
2025
2026
0.0
This is an OmniAuth 1.0 compatible strategy that authenticates via EPFL's Tequila protocol. By default, it connects to EPFL's Tequila server, but it is fully configurable.
2021
2022
2023
2024
2025
2026