Digital Commerce Additional Manual
-
- Page Long Cache Considerations and Configuration
-
Mappings Module
-
Personalization Integrated with JDEdwards
- Sitefinity Images
- Internal Plugins Configuration in Update 6 - SC20220114
- Internal Plugins Configuration in Update 7
-
Content Search Configuration
-
Google Analytics Configuration
-
Task Manager Email Notifications
-
Configure the SmarterCommerce Menu in Backend
-
Management Console Email Templates
- EPayments Modules
-
Troubleshooting Errors
-
Configure Kraken Image Optimization
-
- Page Long Cache Considerations and Configuration
-
Mappings Module
-
Personalization Integrated with JDEdwards
-
How to Add New Widget Template
-
Sitefinity Images
-
Sitefinity Health Check Service Configuration and SmarterCommerce Health Checks
-
Internal Plugins Configuration in Update 6
-
Internal Plugins Configuration in Update 7
-
Content Search Configuration
-
Product Assignments (Filter by Attribute)
-
Google Analytics Configuration
-
Configure Google Maps
-
Cookies Configuration
- Configure SmarterCommerce Menu Backend
-
Sitefinity User Group
-
Copy Settings and Mapping on Multisite
-
Shared Products Module
-
PunchOut Configuration
-
Troubleshooting
-
Token Information
The token revision process works as follows:
When the plugins are used, the first thing it does is validate that the MC Token is a valid token in the security tables. When doing this validation, we generate an encoded token (AuthToken) which is the one we use to know if our internal services are valid.
The process then each time it calls a service checks the MC's token and then checks that the AuthToken is valid. When it is not valid, the services will not be executed, and an error will occur in the plugins.