-
Notifications
You must be signed in to change notification settings - Fork 176
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
Facebook workplace with microsoft SSO doesn't work #70
Comments
I'm marking as a nice to have for now. If someone has compelling evidence that Workplace actually has significant adoption, we can potentially raise the priority. |
@pauljt Would being able to add Microsoft SSO properties into he Facebook container help? Something like this: |
Hi, I also have a similar issue. My company uses single sign-on. When trying to login I end up with the following message. |
Same issue here, our company is using ADFS for single sign-in. After logging in, I receive a 404 message saying Workplace cannot find the saml.php page. |
We have the same issue, although at least instead of permanent loop when we try to log in to facebook workplace we get just this error page: Unfortunately this means that nobody at our company is able to use the extension. |
Hi, are there any updates on this? |
Its also not working with single sign on with Google accounts! Its having infinity redirect! |
Also wanted to report this issue with Google SSO and Workplace. Users get stuck at https://company.facebook.com/work/saml.php with a 404 error. Having an option to add Google to Facebook container should be enough I think. I would also like to ask for this to be considered bug and not an enhancement, since this add-on is unintentionally breaking the behaviour of Workplace. |
My F@W still not working. Any update or something similar? |
Nothing yet, but we are triaging and prioritizing these issues, so upvotes are helpful! |
Enables SSO login for workplace via jumpcloud. More domains can be added to SSO_DOMAINS as required.
Enables SSO login for workplace via jumpcloud. More domains can be added to SSO_DOMAINS as required. Also add f8.com
My company are also using it now, and we're 60+K users, all using Microsoft SSO... Would really appreciate you adding support for that... |
We are working on a release that will allow users to add sites into the Facebook container when trying to log in. We designed it for the use-case where someone uses Facebook as their SSO provider, but it may help this situation too. Please watch this space and help us test it when it's released. |
Hi, |
@Acid-Crash Yes – But we only support that feature on sites that have "Login with Facebook" on sites outside of the Facebook Container. Example: https://imgur.com/signin If I'm reading the issue correctly, the sign in method is using Microsoft SSO INSIDE the Facebook Container (on Workplace) and attempts to connect outside the container to MSFT, breaking the log in process. We have a feature in the works to manually add sites to the Facebook container. Follow it here: #422 |
Closing this issue for now. As mentioned, I referenced this issue in #422 to be part of the testing params. Thanks! |
Same problem at my work. Is this enough evifdence that this is more than a "nice to have" now? |
I am also having this problem "Facebook workplace with microsoft SSO doesn't work". Why is this issue closed? |
Still applicable, the #422 does not fix this, it's impossible to remove workplace from container. |
@yoctozepto I think it is the inverse – the fix for this is to add Microsoft.com (which covers its' subdomains) to the Facebook container. |
Thanks, @maxxcrawford, I misread last comment. I had to add "microsoftonline.com" but now all other microsoft sites, including office, go crazy with broken redirects... I guess one can't have the cake and eat it too. |
@yoctozepto Ugh. I imagine you'll need to continue to add those sites to the Facebook container too to get past the redirects. It's a bit of a goose chase. 😦 |
I'm going to piggyback on this topic because I think my problem is related. I'm getting a 403 Error: app_not_configured_for_user when I try to open my university's Workplace page. This was working fine until this morning. I had powered down the computer last night and it began when I restarted today. I suspect this may be coincidental since I have done this several times within the past few days (storms in the area). This is happening on MS Edge for Mac, which is my preferred browser. I was able to log in to Workplace from Safari. Here is a screenshot of the error info: Thanks for the help. |
@TonyCr46 Are you using this extension in other browsers? Facebook Container is currently only supported in Firefox desktop (due to Containers technology). |
@maxxcrawford I'm not sure what you mean by extension. This is happening when I open the web page xxxuniversity.workplace.com. It was working in Edge up until yesterday. It's working fine in Safari now. |
@TonyCr46 this is a bug report against Mozilla's Facebook Container extension to Firefox desktop, not Facebook. (BTW, xxxuniversity sounds very NSFW ;-) ) |
OOPs. My mistake. Thanks for the heads-up. |
Up to today, I still have this issue |
Do we expect any updates on this issue? |
This issue is still not solved for workplaces that use Microsoft SSO, #422 does not solve it, adding Microsofts login sites to Facebook Container gives problems for all other sites that Microsoft SSO. Adding all those sites to Facebook Container may remove the login issue but completely defeats the purpose of having a container in the first place... |
Issue remains with Google SSO as well |
Report via email:
My workplace uses Workplace by Facebook (https://www.facebook.com/workplace) and it does not work with the Facebook Containers add-on installed in Firefox. Facebook Containers is still active since it uses the Facebook domain when accessing Workplace by Facebook (http://work.facebook.com)
What happens when trying to login is a perpetual loop where it opens our single sign-on page (in this instance Microsoft) only to close it again. Keeps happening until you close the tab.
The text was updated successfully, but these errors were encountered: