We hade set Windows login in Business Central on premises instance and during database refresh was requested to add login via Microsoft Entra.
The process has nothing to do with the database. All configuration is local. It is well described in this official documentation. What I did.
- IIS site, tab Authentication, Windows Authentication Enabled on HTTP 401 Challenge
- IIS site file root
- find file navsettings.json in C:\inetpub\wwwroot\BCDEVname\
- switch ClientServicesCredentialType to value "AccessControlService"
- restart IIS
- Microsoft Entra App registration settings
- create new registration https://entra.microsoft.com
- set redirect URI https://xxx.xx/SignIn
- api permissions for "User.Read"
- expose an API
- set application ID uri to the format of https://xxx.xx/ ideally
- go back to overview and click button "Endpoints" to see URLs
- MMC console for Business Central button edit
- Tab general
- Credential Type: AccessControlService
- Uncheck "Disable Token-Signing Certificate Validation"
- Tab Azure Active Directory
- Application Client ID: <insert ID from App registration in Azure>
- WS-Federation login endpoint: https://login.microsoftonline.com/<tenantID>/wsfed?wa=wsignin1.0%26wtrealm=<applicationApiIdUri>%26wreply=https://xxx.xx/SignIn
- Metadata endpoint: https://login.microsoftonline.com/<tenantID>/FederationMetadata/2007-06/FederationMetadata.xml
- save and restart BC instance
- if errors then check event viewer on server: Windows logs / Application.
Next time you open https://xxx.xx/ you will be redirected to AAD Entra login page.
Žádné komentáře :
Okomentovat
Dotaz, připomínka, oprava?
(pokud máte problém s vložením příspěvku, vyzkoušejte to v prohlížeči Chrome)