{"id":33776,"date":"2023-01-17T15:19:45","date_gmt":"2023-01-17T09:49:45","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=33776"},"modified":"2023-01-20T17:17:05","modified_gmt":"2023-01-20T11:47:05","slug":"how-to-solve-500-internal-server-error-using-dynamics-crm-web-resource-html-as-a-redirect-url","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2023\/01\/how-to-solve-500-internal-server-error-using-dynamics-crm-web-resource-html-as-a-redirect-url\/","title":{"rendered":"How to solve 500 internal server error using Dynamics CRM web resource (HTML) as a redirect URL"},"content":{"rendered":"

Overview<\/strong><\/h2>\n

Recently, I was working on functionality where we needed to generate access and refresh tokens for third-party apps in Dynamics CRM 365. I had a button on the ribbon bar that would send an OAuth\/ authorize<\/strong> request to the third-party app to get an authorization code, which would be returned to a specified redirect URI. However, the OAuth\/authorize request used the code flow method, which always returned the code in the query string parameters with a question mark (?)<\/strong> and we used CRM HTML web resource as a redirect URL. This caused an error message (“Internal HTTP Server Found”)<\/strong> to be displayed in Dynamics CRM 365, as it only accepted query string parameters that started with either #<\/strong> or data<\/strong> keyword.<\/p>\n

Please see the below screenshot of the error message and a question mark in the query string params.<\/p>\n

Dynamics CRM web resource\"Dynamics<\/p>\n

I attempted to solve the issue by embedding the OAuth\/authorize request in an iframe and hiding the iframe, but this did not work. After some research, we came across a suggestion by <\/strong>Scott Durow<\/strong><\/a> and this is our implementation of the same.<\/strong><\/p>\n

I discovered that using a Canvas App as the redirect URI would return the code with an ampersand (&)<\/strong> in the query string parameters. This allowed me to easily retrieve the authorization code using the Params() <\/strong>function of the Canvas App.<\/p>\n

Please see the below screenshot to see how the authorization code gets appended on the query string parameters with an ampersand (&): –<\/strong><\/p>\n

\"Dynamics<\/strong><\/p>\n

You can get the canvas app link from the Canvas App details section below-<\/p>\n

\"Dynamics<\/p>\n

Also, you can get the URI of the Canvas App using the OData query, and below is the screenshot on how to fire the OData query from the browser-<\/p>\n

\"Dynamics<\/p>\n

With the Canvas App as the redirect URI, the authorization code was returned with an \u2018&\u2019<\/strong> in the query string parameters. Using the Params()<\/strong> function of the Canvas App, I was able to retrieve the code and make an HTTP request for access and refresh tokens.<\/p>\n

Now, the code was returned inside the \u2018code\u2019 <\/strong>parameter with the redirect URI, so using the Params(\u201cparameter_name\u201d)<\/strong> function I retrieved the authorization code as seen below,<\/p>\n

\"Dynamics<\/p>\n

Conclusion<\/strong><\/h2>\n

Thus, using the Canvas App, I was able to get the authorization code easily without any error message and the further process of my functionality was running smoothly.<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Overview Recently, I was working on functionality where we needed to generate access and refresh tokens for third-party apps in Dynamics CRM 365. I had a button on the ribbon bar that would send an OAuth\/ authorize request to the third-party app to get an authorization code, which would be returned to a specified redirect\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[18,66],"tags":[2661],"class_list":["post-33776","post","type-post","status-publish","format-standard","hentry","category-dynamics-365-v9-2","category-web-resources-2","tag-dynamics-crm-web-resource"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/33776","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=33776"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/33776\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=33776"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=33776"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=33776"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}