Azure Move from managed to self-hosted developer portal blob storage field missing in srs/config* files and delegation not working #2635
Replies: 3 comments
-
@ShubjeetPal, thank you for opening this issue. We will triage it within the next few business days. |
Beta Was this translation helpful? Give feedback.
-
@ShubjeetPal, delegation requires portal's backend to generate signed delegation URL. You can do so by specifying "backendUrl" setting (pointing to your APIM service) in config.json file of your published website (which you upload to blob storage). However, if you do it right now, you'll get CORS errors which you'll be able to overcome in next few weeks with new CORS settings feature that is being rolled out. |
Beta Was this translation helpful? Give feedback.
-
Thanks @azaslonov. Can you please provide the link for the new CORS setting feature. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Every bug report should have precise description and reproduction steps; console traces or source code references are appreciated.
For assistance requests, contact Azure support or submit a post on Stack Overflow. We don't provide support through GitHub Issues. Feature requests can be raised on the Azure Feedback Forum.
Bug description
The azure document says as below for "Move from managed to self-hosted developer portal" but their is no field in the srs/config* files
The storage account in the config.design.json file needs to be the same as the storage account of the managed version of the portal
The document also does not mention on what needs to be done for delegation as currently it fails with 404
Reproduction steps
Expected behavior
Is your portal managed or self-hosted?
Self-hosted
Release tag or commit SHA (if using self-hosted version)
NA
API Management service name
NA
Environment
NA
Additional context
NA
Beta Was this translation helpful? Give feedback.
All reactions