Common Troubleshooting: Identity
- Sarah Holst
- Jenni Buonanni
- 1 Q: Are my fonts supported in Identity?
- 2 Q: Does Identity support password lockout? If a guest enters the incorrect password, say, 5 times, will Identity lock them out for a period of time?
- 3 Q: Is there an Identity admin screen where I can make theming and language string edits myself?
- 4 Q: Is there a way to require customers to agree to Terms and Conditions prior to creating an account?
- 5 Q: Can my reCAPTCHA threshold vary depending on the user interaction?
- 6 Q: May I use the same reCAPTCHA Application Key/Secret for my Aspenware Commerce site and my Identity site?
- 7 Q: If I use the same reCAPTCHA Application Key/Secret for my Aspenware Commerce and Identity sites can I set different thresholds at each site?
Q: Are my fonts supported in Identity?
A: A single custom font can be supported for those who use CSS to import their custom fonts. Font customizations will apply to the Identity application, but the email font will be standardized as Helvetica for all customers. Supply the font URL to your Aspenware Representative, similar to the example below:
IMPORTANT: At this time fonts are not customizable for those who use Javascript to import their custom fonts. When custom fonts are not available, Identity will use Helvetica and Arial if the browser doesn’t support Helvetica.
Also note that only a single font is supported for Identity, so if headers and body copy require different font libraries, this is not supported today.
Q: Does Identity support password lockout? If a guest enters the incorrect password, say, 5 times, will Identity lock them out for a period of time?
A: No. Identity doesn’t support password lockout at this time, however this functionality is expected to be delivered in the 2.12 Identity release (the release that is compatible with Commerce 2.23 and will be available in late November 2021).
Q: Is there an Identity admin screen where I can make theming and language string edits myself?
A: No. Identity does not have an admin screen presently that is customer-accessible. In the Identity 2.12 release (the release that is compatible with Commerce 2.23 and will be available in late November 2021) an Aspenware internal admin screen is being made available within Azure so that changes can be processed and turned around more quickly by our services team without requiring developer involvement.
Q: Is there a way to require customers to agree to Terms and Conditions prior to creating an account?
A: Aspenware Identity can optionally allow opting into/out of marketing communications when creating an account. For customers that use the separately licensed Loyalty module, Identity also has the ability to enable opting into loyalty programs when creating an account. Marketing communication preferences, as well as Loyalty program enrollment, are flagged and recorded in RTP|One on the customer’s record. Identity does have the option to display a generic T&C checkbox that customers can be required to select as they create an account, however, there is nowhere (no database) that stores any status of whether a customer has opted into this or not, so it’s purely cosmetic, for this reason, Aspenware has not included this in its official documentation as an officially supported feature.
Q: Can my reCAPTCHA threshold vary depending on the user interaction?
A: Unfortunately, Aspenware currently only offers one threshold across all user interactions. Although a threshold of .5 should meet most needs, please let your Aspenware Service Representative know of any issues.
Q: May I use the same reCAPTCHA Application Key/Secret for my Aspenware Commerce site and my Identity site?
A: Yes, you may use the same key for both sites.
Q: If I use the same reCAPTCHA Application Key/Secret for my Aspenware Commerce and Identity sites can I set different thresholds at each site?
A: Yes, the threshold is set at the application level, so you may use different thresholds by setting them in the corresponding admin panel.