{"id":189,"date":"2019-05-11T17:22:13","date_gmt":"2019-05-11T17:22:13","guid":{"rendered":"https:\/\/www.dabbler.dk\/?p=189"},"modified":"2019-05-11T17:28:38","modified_gmt":"2019-05-11T17:28:38","slug":"broken-microsoft-dynamics-365-business-central-single-sign-on-with-multi-tenancy-setup","status":"publish","type":"post","link":"https:\/\/www.dabbler.dk\/index.php\/2019\/05\/11\/broken-microsoft-dynamics-365-business-central-single-sign-on-with-multi-tenancy-setup\/","title":{"rendered":"Broken Microsoft Dynamics 365 Business Central Single-Sign-On with Multi-Tenancy setup"},"content":{"rendered":"\n<p>After having a Single-Sign-On (towards Azure Active Directory)\/Multi-Tenancy setup running on Dynamics NAV 2018 for some time, I tried to create the same setup with Microsoft Dynamics 365 Business Central 2018 fall release.<\/p>\n\n\n\n<p>And to my surprise it failed with this error just after logging in: &#8220;The value for the WSFederationLoginEndpoint configuration settings cannot be empty.&#8221;. My  &#8220;WSFederationLoginEndpoint&#8221; setting was NOT empty, so the error does not make any sense.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"579\" height=\"277\" src=\"https:\/\/www.dabbler.dk\/wp-content\/uploads\/2019\/05\/Error.png\" alt=\"The value for the WSFederationLoginEndpoint configuration settings cannot be empty.\" class=\"wp-image-193\" srcset=\"https:\/\/www.dabbler.dk\/wp-content\/uploads\/2019\/05\/Error.png 579w, https:\/\/www.dabbler.dk\/wp-content\/uploads\/2019\/05\/Error-300x144.png 300w\" sizes=\"auto, (max-width: 579px) 100vw, 579px\" \/><figcaption>The value for the WSFederationLoginEndpoint configuration settings cannot be empty.<\/figcaption><\/figure>\n\n\n\n<p>It puzzled me for a while because these setups was working without any problems:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Dynamics NAV 2018, Single Tenant<\/li><li>Dynamics NAV 2018, Multi Tenant<\/li><li>Dynamics 365 Business Central 2018 fall release, Single Tenant<\/li><\/ul>\n\n\n\n<p>So the Single Tenant BC was working, but failed as soon as I configured it for Multi Tenancy.<\/p>\n\n\n\n<p>Finally after weeks of messing around I gave up and reached out to my contacts from Microsoft Development Center Copenhagen to see if they could help me solve the issue (first I off cause raised a ticket with Microsoft Support). Luckily Freddy from <a aria-label=\" (opens in a new tab)\" href=\"https:\/\/freddysblog.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/freddysblog.com\/<\/a> knew <strong>exactly<\/strong> what was wrong with my setup &#8211; and was able to send me the exact solution. And made the effort to do this on a Saturday morning! \ud83d\ude42<\/p>\n\n\n\n<p><strong><font color=\"#004000\"><a aria-label=\"THANK YOU FREDDY :-) !!! (opens in a new tab)\" rel=\"noreferrer noopener\" href=\"https:\/\/freddysblog.com\/\" target=\"_blank\">THANK YOU FREDDY \ud83d\ude42 !!! &#8211; please click here to visit his blog!<\/a><\/font><\/strong><\/p>\n\n\n\n<p><\/p>\n\n\n\n<p>Oh &#8211; I almost forgot. If you have this error, empty these configurations settings from the Service Tier:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>AzureActiveDirectoryClientId<\/li><li>AzureActiveDirectoryClientSecret<\/li><\/ul>\n\n\n\n<p>These two settings are used in Dynamics NAV 2018, but should be left empty in Microsoft Dynamics 365 Business Central.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>After having a Single-Sign-On (towards Azure Active Directory)\/Multi-Tenancy setup running on Dynamics NAV 2018 for some time, I tried to create the same setup with Microsoft Dynamics 365 Business Central 2018 fall release. And to my surprise it failed with this error just after logging in: &#8220;The value for the WSFederationLoginEndpoint configuration settings cannot be &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/www.dabbler.dk\/index.php\/2019\/05\/11\/broken-microsoft-dynamics-365-business-central-single-sign-on-with-multi-tenancy-setup\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Broken Microsoft Dynamics 365 Business Central Single-Sign-On with Multi-Tenancy setup&#8221;<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":190,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,5],"tags":[32,25,24,34,26,33],"class_list":["post-189","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-nav","category-software","tag-business-central","tag-dynamics","tag-microsoft","tag-multi-tenant","tag-nav","tag-single-sign-on"],"_links":{"self":[{"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/posts\/189","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/comments?post=189"}],"version-history":[{"count":12,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/posts\/189\/revisions"}],"predecessor-version":[{"id":421,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/posts\/189\/revisions\/421"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/media\/190"}],"wp:attachment":[{"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/media?parent=189"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/categories?post=189"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dabbler.dk\/index.php\/wp-json\/wp\/v2\/tags?post=189"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}