Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ: buzzfeed-fork #382

Closed
wants to merge 4 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions content/faq/buzzfeed-fork.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: "What about the Buzzfeed fork of the Bitly proxy?"
description: 'The Buzzfeed SSO proxy has been labeled a "fork" of the Bitly OAuth 2 proxy; but it technically shares very little, if anything.'
tags:
- Buzzfeed
- Bitly
- OAuth 2
---

## Question

What about the Buzzfeed fork of the Bitly proxy?

## Answer

The Buzzfeed SSO proxy has been labeled a "fork" of the Bitly OAuth 2 proxy; but it technically shares very little, if anything. At least they ripped out support for all other SSO authentication providers aside from Google. Also, it does not support WebSockets, which is needed by the Kubernetes Dashboard. If you're already leveraging Google (G Suite) SSO, then it doesn't matter, since that's the out-of-the-box support . If you’re using another SSO provider (e.g. AWS or Okta), then support is probably lacking.

We can support the Buzzfeed SSO proxy. However, depending on your SSO provider, there maybe be some R&D associated with it.