This blog article will walk you through the required steps on how to install GroupCalendar and ActivityTools in a claims-based environment.
This article is valid for GroupCalendar for CRM 2011, 2013, 2015 and 2016 but only for CRM 2013 and older versions of ActivityTools. From CRM 2015 onwards ActivityTools does not have to be configured for IFD anymore!
The steps are the same for both products, so instead of an explicit product name, we will use the term the addon in this guide.
The IFD configuration for the GroupCalendar is as follows:
Before you start the installation, make sure that MS CRM is working correctly in IFD/Claims-Mode, including your ADFS, which should be installed correctly and configured to work with MS CRM.
More details on how to configure MSCRM for IFD/Claims can be found in the Microsoft Guide Configuring Claims-based Authentication for Microsoft Dynamics CRM 2011 Download
The following system configuration is the base for our guide.
Your setup will differ in these URLs, make sure you are replacing the URLs with your own URLs when following the guide.
Internal Url used to access Microsoft Dynamics CRM:
External Url used to access Microsoft Dynamics CRM:
AD FS Server:
The addon itself also requires a dns name:
https://activitytoolsserver.rc1ifd.ptm-edv.at (for ActivityTools)
https://groupcalendarserver.rc1ifd.ptm-edv.at (for GroupCalendar)
Basic installation/configuration of the addon:
We have finished the configuration of the CRM part and now need to configure the AD FS.
You have finished the configuration and you should be able to use the addon in your IFD/Claims Environment now.
Figure 5: Error Message
This indicates you are using a wrong certificate for the ADFS signing.
Make sure the thumbprint in the web.config matches the one the token signing certificate in ADFS.
Figure 6: Error Message
This error could (also) indicate access rights problems with the certificates private key (mainly an issue for self signed certificates).
Open your certificate store on the server (MMC, add certificate snapin for local computer) and find your HTTPS certificate. In the context menu, under all tasks select the manage private keys option and grant access to everyone.
Checklist for general troubleshooting:
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to email@example.com.