When SSO is enabled, by default storefront acces is using it instead of the explicit form. And some multi-account users can start grunting. We can force the display of the explicit form by editing the CtxsAuthMethod cookie in ReceiverFolder\custom\script.js :
When you rename a farm name, when you access to bindings that integrate this farm, the console crash… The workaround is to remove the farm from the bindings, rename it and re-append it into the bindings
After installing a certificate, activate the connection and change base url … It’s a catastrophe! Nothing is currently working on the Storefront, it fails with an error message: “Unable to process request” The first reaction is often disable the loopback communication, which ultimately is not optimum: in the case of …
Nous avions initialement installé notre serveur StoreFront sans activer SSL, puis d’activer ce mode dès que l’accès Web était fonctionnel . Une fois le certificat émis par notre CA, nous avons utilisé la méthode IIS Manager (http://www.iis.net/learn/manage/configuring-security/how-to-set-up-ssl-on-iis) pour ajouter notre certificat. Sans surprise, l’accès Web en https fonctionne correctement! L’étape suivante …