How to use Azure CDN with disabled anonymous blob access?
Looks like as of August 2023 anonymous access to storage accounts has been disabled. I am trying to create a CDN which will host javascript file(s) for various corp-wide related apps to use.
Since anonymous access is disabled, how can I give read access to consumers of my Azure CDN?
When trying to view the CDN endpoint (using a browser) i keep getting this error:
<Code>PublicAccessNotPermitted</Code>
<Message>Public access is not permitted on this storage account.</Message>
I know there are SAS tokens, but they have an expiration, so I dont feel this is a viable solution.
What are viable solutions to resolve this CDN/storage access issue? It seems like disabling anonymous access kind of makes the general use-case for CDN's to be obsolete.
Right now Im kind of at a roadblock and seriously just considering publishing my javascript(s) as a node package.
Updated
I have to double check this, but it looks like I got unblocked by adding a adding a System user identity on the CDN with role of Reader.
Updated (3 days later)
Upon verifying things today I am not able to access things again on the CDN endpoint. So I am back to the drawing board on this one.
If your blob storage endpoint is configured to disallow anonymous read access, you should provide a Shared Access Signature (SAS) token in each request you make to your Azure CDN domain.
By default, anonymous read access is not allowed for blob storage endpoints. If your data should be publicly available, you can explicitly enable anonymous access for the blob storage. To allow public access for a storage account, perform the following steps:
- Navigate to your storage account in the Azure portal.
- Go to Settings → Configuration section.
- Set Blob public access to Enabled and click "Save":
I have just checked one of my storage accounts where anonymous access is enabled and it works as expected with the configuration shown above.
- Node.js recursive calls with q framework for multiple GET requests
- How to Decode and Verify OCSP Response in TypeScript with pkijs for Certificate Validation
- Firebase and Node.js application results in the requested URL was not found on this server for the firebase serve command
- Can I determine if a string is a MongoDB ObjectID?
- Husky add command is deprecated?
- Solidity compiler error loading specific function
- error could not determine Node.js install directory
- How can I sort an array?
- Make a link from Electron open in browser
- Prisma query engine not found on mac M1
- response.clearCookie() followed by response.cookie() leads to 2 same-name cookies
- Cannot read properties of undefined (reading 'statusCode') Nodejs using cheerio
- WebSocket connection to wss failed in production only(front end and back end on different domains)
- Puppeteer cant listen all request from paribu.com
- Disable deprecation in javascript console
- messaging.sendMulticast is not a function
- Node.js fs.readdir recursive directory search
- How to specify local registry in yarn?
- Handle Cors from lambda to cloudfront or s3
- Where can i see in amplify app the console log
- generate *.story.ts automatially when generating Angular component by cli
- Node.js native addons: where is node_api.h located?
- Errors building supergraph with Docker, Node.js, and Apollo's rover
- Postman POST call works Angular doesn't
- How to change console.log() output in VSCode?
- nodejs server create file name 4000, when server started
- Uncaught TypeError: PouchDB is not a constructor
- The difference between "require(x)" and "import x"
- Uncaught Error: Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function but got: object
- "npm run dev" Command Doesn't Work - Giving "missing script: dev" error