If you configured Claim forwarding in the Ambient Data Framework for custom Footprints, you may have chosen to configure a different cookie name than the default, TAFContext. If so, you must also configure that custom cookie name in the Experience Manager configuration.
Procedure
- Access your Content Manager server and navigate to %TRIDION_HOME%.
- Navigate to the subfolder web\WebUI\Editors\SiteEdit\Configuration\ and in this location, open SiteEditEditor.config for editing.
- Under the
footprints section, find the footprintscookienames section. In this section, you can configure an overall cookie name, and you can also configure a specific cookie name for a Publication Target, which overrides the overall cookie name.
- To configure an overall cookie name, in the
footprintscookienames element, change the value of the default attribute to the custom cookie name you configured in the Ambient Data Framework configuration.
- If you are using the deprecated publishing framework, you can also configure a specific cookie name for a specific Publication Target by adding a
footprintscookiename element inside the footprintscookienames element, and setting its attributes as follows:
publicationtargeturi
-
Set to the Content Manager URI of the specific Publication Target.
name
-
Set to the custom cookie name you configured in the Ambient Data Framework configuration.
- Similarly, if you are using the new publishing framework, you can configure a specific cookie name for a specific Target Type by adding a
footprintscookiename element inside the footprintscookienames element, and setting its attributes as follows:
targettypeuri
-
Set to the Content Manager URI of the specific Target Type of the Business Process Type.
name
-
Set to the custom cookie name you configured in the Ambient Data Framework configuration.
- Save and close SiteEditEditor.config and restart IIS.