I would like to log the "Event URL" field in Kentico Portal logs to Azure Application Insights for 404 requests. Since I changed my custom page for 404 errors in Kentico Portal I only get "PortalTemplate.apsx" for the url field in the requests table in AppInsights.
We already have this as a recommendation on the GitHub - use RawUrl instead of Request.Url.
As explained here RawUrl better suites cases when the request was redirected to the custom error page: Request.RawUrl vs. Request.Url
Please upvote the issue on GitHub. As a workaround now you can replace OperationNameTelemetryInitializer in ApplicaitonInsights.config to your own implementation of it that uses RawUrl instead of the Url.
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
Ok so for multiple reasons, I changed the network settings of an app service so that it cannot be accessed using its .azurewebsites.net url
It works but it displays the default "Forbidden" page. What I would like to do is have it display something like this:
If I can extend it to returning a failed status instead of a 403, that would also be awesome.
Creating custom error pages in cases of 4XX and 5XX errors is not supported out of the box with Azure App Services as of today, but it is a heavily upvoted and requested feature on their UserVoice forum. Please upvote it so the Product Group can prioritize it accordingly.
To work around it, you could use an Application Gateway to create custom error pages instead of displaying default error pages. You can use your own branding and layout using a custom error page.
Custom error pages are supported for maintenance and unauthorized access scenarios, and can be defined both at global and listener levels.
The configuration through Azure Portal and Azure PowerShell is explained in detail in this article: Create Application Gateway custom error pages
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".
I have completed all steps properly according to the following sample.
https://github.com/Azure-Samples/active-directory-b2c-dotnet-uwp
I have completed all optional steps as well, but when I test Run Now my SignUpSignIn Policy through azure portal, it keeps loading for a while and then just displays blank white page. I am pretty confident I have configured everything properly my only doubt is the Custom Redirect URI which I have set as following :
com.onmicrosoft.fluensoft.fluennative://redirect/path
fluensoft is my tenant name
fluennative is my native app name
in case of web app/ web api there are clear instructions that redirect uri is an http call, but in case of native custom redirect uri it is very confusing.
Solution :
It was actually a network problem for that specific attempt when I tried the demo, I tried it again the next day and now it works as expected, If you are having the same problem then check your network in developer tools, also check the console just in case.
I am working on Azure App service API apps.
I followed the steps available in the below link, for implementing user authentication concept to the ToDoListAngular project and successfully deployed in azure, but when i test with the ToDoListAngluar project azure url to add the todoitem it shows error on Google Chrome Address bar "This page is trying to load scripts from unauthenticated sources".
https://azure.microsoft.com/en-us/documentation/articles/app-service-api-dotnet-user-principal-auth/#overview
Please tell me how to resolve the above error.
It sounds like one of your API Urls does not have https:// at the beginning.
My best bet is the "toDoListAPIURL" in your front end site's application settings on the portal. There are a ton of API urls in the source code to check if that doesn't do it. Going back through the getting started tutorial should have them all.