I've added my function app to API Management in Azure.
My function app has an undesirable name swanky-function-app - and I want to change it.
When API management mounts it, it gives it a default URI of /swanky-function-app which is undesirable.
When I change the URL field to something nicer such as /some-new-path, when I test it, it 404s.
How do I customize the URL without it 404ing?
If you are setting up in APIM, you just need to est the url suffix value if you want to change the url,
You can add a URL rewrite policy. Select the operation, go to "Inbound processing", add policy, choose "rewrite-uri". Fill in the original route in the backend field, for frontend it should already show the URL that you chose in the Frontend URL settings (shown in window above)
I don't think that's the way it should be, but at least it works
Related
We have docusign integrated in our platform & all of a sudden we are getting error from DocuSign
"The redirect URI is not registered properly with DocuSign".
We have proper & valid redirect uri configured in the application.
Please Note that exsisting setup is working fine, for newer apps or newer accounts, it is throwing the above-mentioned error Here is the screenshot of the same .
The redirect uri is valid as it's working for other app.
Has something changed at DocuSign end recently?
Update:
As asked, Please find the redirect uri screenshots below (I've masked the host url),
DocuSign Redirect URI configuration - Please note that both URI are same with difference in host url.
Complete Oauth request url
Redirect window
Make sure to compare the URL you see in the browser to the one in the IK. Make sure it's the same IK, in the same env (production vs. developer env is different!). Even a tiny difference between the two URLs will fail this. You need to URL decode the redirecUri from the main URL and then use that by copy/pasting it into the apps and keys page.
Then wait about 1-2 minutes before trying again.
Edit: confirmed that the URLs DO NOT MATCH, and that is the issue. The URLs must match 100% for this to work
Redirect URIs are specific to each integration key (application) and do not get copied over if you make a new integration key. Based on your description it sounds like you have created a new integration key. I would recommend visiting the Apps and Keys page on your DocuSign Admin settings and adding the redirect URI to the new integration key. Here is a support centre article which outlines this including the steps for how to add a new redirect URI
Nothing in this area has changed on DocuSign AFAIK.
Check that the redirect URI specified in your initial OAuth redirect is the exact same as the URI you set in the Integration Key's settings page.
The redirectURI cannot include any dynamic data including query parameters, etc.
You can use the settings tool's Apps and Keys page to delete and then re-add the RedirectURI. Check carefully that it doesn't include any trailing spaces, etc.
After you've made a change via the Apps and Keys pages, wait 5 minutes before attempting to use the Integration Key.
Ensure that you're using the right Apps and Keys page. If your app has passed go-live then:
For the production systems, use the apps and keys page from docusign.net
For the developer (demo) system, use the apps and keys page from demo.docusign.net
Can't seem to pin down the correct order of operations here if it exists...
Current setup:
I have user.mysite.net pointing at application gateway public ip. test.mysite.com/user1 is pointing at a VM hosting a hello world application. This VM exists in the same tenant but different subscription. The app is just a simple hello world app.
Target state:
I want to configure the rewrite or redirection, so that when I hit user.mysite.net in my browser it should send me to test.mysite.com/user1, but at the same time, within the browser I don't want to change the url, I want to preserve the original url: user.mysite.net
Is this possible? If so, how would I even go about configuring it or order operations? i.e what would the rewrite rules look like and then do I attach it to a routing rule with redirection or backend?
In the case of a URL rewrite, Application Gateway rewrites the URL before the request is sent to the backend. This will not change what users see in the browser because the changes are hidden from the user.
Please check if you can do pattern matching with the location header matching eg. IF contains mysite.net and Perform an action to rewrite the location header appGW -rewrite-http-headers-url.
Other wise it may not be possible with rewrite,if it is external site url and the original site has to appear in address bar .See Reference -Stack Overflow
NOTE: URL rewrite feature is only available on Application Gateway v2
SKU. You can follow the documentation here to implement rewrite
URL path.
Reference:
Rewrite URL and query string with Azure Application Gateway - Azure portal | Microsoft Docs
I’m trying to make a GET request in order to query data from Azure Search service. I am trying to follw this tutorial:https://www.dotnetcurry.com/microsoft-azure/cognitive-search-rest-apis-angular-app
How can I allow my domain to make a successful GET request without being blocked by CORS policy.
Is there a possible way or custom configuration on Azure to allow default sites to bypass this error? I have tried to add the API key as a parameter to the URL but the same problem raised again.
Thank you
You see this message because your browser blocks requests going to host samplecognitive.search.windows.net which is different from the origin localhost. You must tell Azure Search to send back a "Access-Control-Allow-Origin" header including localhost.
In the Overview tab of Azure Search Service go to "Indexes" and click on your index. Then go to "CORS". Add http://localhost:4200 and click "Save".
We are migrating our old site on prem to a new one hosted on Azure but we need to maintain the old site online.
So imagine the following scenario:
new site: www.site.com
old site: www.oldsite.com
This is what we need:
if a user enter www.site.com/somepath and "/somepath" doesn't exist (url not found), it must be redirected to the onprem www.oldsite.com/somepath
Is it possible? How to write the Azure application gateway rule for url not found?
Thank you in advance, Marco
URL path based rules support notion of default path which is used when none of the path rules match. In your scenario you could set a default backend pool which redirects user to oldsite.com/somepath for any request received. You can then configure path based routing so that site/somepath goes to new pool, site.com/somepath2 goes to another pool.. if none of the url paths match the request would be sent to default pool from where it could be redirected to oldsite.
I believe you are use a URL Redirect to achieve this.
Create an application gateway with URL path-based redirection using Azure PowerShell
https://learn.microsoft.com/en-us/azure/application-gateway/tutorial-external-site-redirect-powershell
In addition, if you open the links provided and look to the left you will see even more options. Some of which you might find useful.
When a portal application is run using RAD/ or any IDE, the portal server will generate a random URL for the application, which expires after some time.
If I had an portal application like HelloWorld, how do I get a permanent URL like:
myportal/HelloWorld/
instead of a randomly generated URL. This question could also be asked like, how can I get a unique URL to my portal application
When you go to place a portlet in a more permanent place in your Portal, you will create the page yourself rather than letting RAD generate something random for you. Part of the options for a page is a friendly URL. So you could specify what URL you want after the /wps/myportal/. Here is a link to some basic documentation about creating pages.
If you want smth like /wps/myportal/HelloWorld you need create portal page and give it friendly name. Then you can deploy and place you portlet application(s) on this page.
If you to have application outside portal context (servlet for example), you need deploy it to WAS directly and set desired context root to get yourserver:10039/your/app/context