I noticed something strange in Sitecore; for most of my nodes (not the Sitecore node!), the 13th Hex character of the identifying GUID is ‘4’.
I had a list of about 50 of these, and my eye was drawn to the pattern. Now, I thought Guids were entirely random, except that the chance of 50 page template IDs all having a 4 at that character was infinitesimal.
Weird. Except it turns out that they’re not random. I had no idea that there are different versions of guids, or than that character defined the version of the GUID.
This requires a test, so I wrote a program to print Guid.NewGuid() a lot:
All of them are 4s.
- GUIDs aren’t entirely random.
- They might not be very random at all, looking at some of the other GUID versions.
- Which is why they shouldn’t be used as a source of entropy for encryption.
- I still have things to learn.
I’ve written before about Azure Backup fails due to Content Testing Screenshots not clearing and the resulting problems with backup size.
That’s not the whole problem though.
Sitecore made some effort to configure some directories to be outside the home folder of the app services, and therefore not subject to backup – but there’s still a lot that shouldn’t be in the backup. Continue reading “Keeping the size of of Sitecore Azure Backups under control”
I tried logging into Sitecore’s App Center, and got the following error:
The credentials used to log in to the Sitecore App Center cannot access the license used on this server
This was in Chrome. Strangely, I discovered that I could log in through Chrome Canary. What’s different?
Continue reading “Sitecore App Center Login Fails”
We have been having a problem with Sitecore in Azure PAAS – it appears that when auto-scaling scales out, App Services are being put into rotation before they have started up. This is causing all sorts of weirdness.
Sitecore support recommended making sure that we had Application Initialization configured. That seems a good idea. I’m not sure why the guys who set up this instance didn’t; perhaps they were unaware of it (and to be fair, it’s something I’ve not looked at before).
Continue reading “Application Initialization for Azure Service Apps (and Sitecore)”
Sitecore’s Federated Experience Manager (FXM) allows non-Sitecore sites to record analytics data into Sitecore. It’s both quite neat, and has a number of problems. I’m going to assume you’ve done a little reading about FXM already, but here’s how it works (in Sitecore 9.0.x).
And the response to that sets up a Sitecore Session ID, Contact ID, and returns element matches, which are stored in Cookies:
The element matches use HTML Element IDs to identify content to a) attach click handlers too, or b) elements to insert content around or in place of.
This is where we hit the first of my problems with FXM… Continue reading “My problems with Sitecore FXM”
We had a problem with Sitecore 9.0.2 in a PAAS environment. Our Azure App Service backups started failing. This was due to the backup size:
Above 10GB you have to use an Azure Storage Account to store your backup, apparently. However, we wondered why our backups had grown so large – they had been a few GB – and why they seemed to be growing. Continue reading “Azure Backup fails due to Content Testing Screenshots not clearing”
So, the SIF install scripts for Sitecore create certificates for securing the XConnect communication. There are 4 certificates involved – 2 “DO_NOT_TRUST_XXX” trusted root certs for signing 2 other certs, and those 2 are a) for the IIS XConnect site binding (as normal with HTTPS), and b) one for the XConnect client.
Unfortunately, these only last for a year… and the process of renewing them isn’t well documented. Continue reading “XConnect certificate expiry”