Philanthropy Cloud

Philanthropy Cloud

  • Languages iconEnglish
    • Français

›SSO Guide

User Guide

  • Introduction
  • User Interface
  • Donate
  • Volunteer
  • Appendix

Admin Guide

  • Introduction
  • User Interface
  • Onboarding Workflow
  • Reports
  • Settings
  • User Management
  • Donation Management
  • Integration
  • Content Management
  • Tax Receipts and Pledge Confirmation Emails
  • Batch Pledge Entry
  • Branding
  • Home Page
  • Appendix

iOS Mobile Guide

  • Introduction
  • Installation
  • Featured
  • Explore
  • Profile
  • Donations
  • Volunteering
  • Appendix

Android Mobile Guide

  • Introduction
  • Installation
  • Featured
  • Explore
  • Profile
  • Donations
  • Volunteering
  • Appendix

SSO Guide

  • Introduction
  • Single Sign-On
  • Upload Employees
  • Identity Providers
  • Workplace Interactions
  • Mobile Applications
  • Best Practices
  • Troubleshooting

Troubleshooting

Below are some common issues you may encounter and possible resolutions when onboarding customers:

  • Federation ID is case-sensitive. If the federated identity is your organizational email address, be sure to enter it exactly as AD FS sends it. Otherwise, Salesforce cannot find a matching user. Unfortunately, you cannot write a custom claim rule to normalize the case of the LDAP attribute before sending it because the claims language has only a basic regular expression replace.

  • Assertion has expired. Assertions with a time stamp more than 5 minutes old are rejected. Note: Salesforce does make an allowance of 3 minutes for clock skew. Therefore, an assertion can be as much as 8 minutes past the time stamp time or 3 minutes before it. This amount of time is less if the assertion’s validity period is less than 5 minutes. Ensure that your AD FS server’s system clock is synchronized to a good internet time source using Network Time Protocol (NTP).

← Best Practices
Philanthropy Cloud
Copyright © 2021 Salesforce.org