1
votes

I have a custom ADB2C policy that specifies <ContentDefinition> tags to use custom HTML. The custom HTML is stored in Azure Blob Storage.

The problem I have is that when I upload a new version of the custom HTML the changes don't show up when I go through the policy (unless I leave it overnight). I suspect that there might be some caching going on, but none of the documentation I have seen mentions caching.

Is there a way to disable/clear the cache, or might there be something else wrong that has similar symptoms?

The new files are definitely in the blob storage as I can request them directly in a browser and get the latest versions.

I can also upload the new html files with new names and tweak the policy to point to the new names, so I'm fairly confident I'm not making a silly configuration mistake.

1

1 Answers

1
votes

AAD B2C does not cache or download your HTML file. AAD B2C drops JS to tell the client to download the HTML, then client side JS that AAD B2C delivered, will have the client merge the HTML file with the content on the page. The problem here is to do with the client browser caching the HTML file. You can prove this by using Incognito/Private mode usually.

You can see more info here on how this process works: https://docs.microsoft.com/en-us/azure/active-directory-b2c/customize-ui-with-html?pivots=b2c-custom-policy#custom-html-and-css-overview