This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Are there known issues with Salesforce SSO and the Dutch Language Pack?

  • 4 àwọn èsì
  • 1 ní ìṣòro yìí
  • 1 view
  • Èsì tí ó kẹ́hìn lọ́wọ́ Bill_S

more options

We are using Salesforce (CRM) SSO registration and sign in for our Community. When a Dutch language user clicks on the Register link for our community, using FF, he gets a default page pulled somewhere out of Saleforce that we do not use. Since we do not support the Dutch language, he should be getting the English version of the Registration page. Instead he gets some default Salesforce sign-in page that we don't even know where it comes from. No other languages cause this issue, and we don't see this happen with Dutch on Chrome or IE. We're using FF 16.

We are using Salesforce (CRM) SSO registration and sign in for our Community. When a Dutch language user clicks on the Register link for our community, using FF, he gets a default page pulled somewhere out of Saleforce that we do not use. Since we do not support the Dutch language, he should be getting the English version of the Registration page. Instead he gets some default Salesforce sign-in page that we don't even know where it comes from. No other languages cause this issue, and we don't see this happen with Dutch on Chrome or IE. We're using FF 16.

All Replies (4)

more options

Can you try clearing cache and cookies to see if it'll help? - See Delete browsing, search and download history on Firefox on how to do that.

more options

We know to do that first thing - clearing cache.

more options

Did you try to install the Dutch language pack or set the nl language (pref: intl.accept_languages) as the default to check what gets send to the server and check the response?

more options

This issue only occurs when the Dutch language pack is installed and set to default (on top). Setting the language preference in the url to nl returns the correct page.