![waves central update fail waves central update fail](https://central.owncloud.org/uploads/db1708/original/2X/f/fdb99f9e294639ea46548436b47e8ca9d869f1f9.jpeg)
But when Basic Auth will be removed, also for doing testing on sandboxes you need to register applications into AAD, grant permissions and so on, a task that normally cannot be done by a Business Central developer. With Basic Auth support on sandbox, it’s quite easy to do so (just setup your user and you’re ready to go). Last personal opinion is related to the Sandbox environment: it’s quite a frequent case to have the need to test applications or integrations on the sandbox environment quickly. All the external integrations with Dynamics 365 Business Central actually works silently (without user interaction) and to permit this with OAuth2, service-to-service authentication flow must be supported absolutely. The other problem is the OAuth2 flow to support. Not all external services and external clients are ready to support OAuth2 soon or CAN support OAuth2. Normally the most common scenarios are external services that must connect to Dynamics 365 Business Central SaaS from the outside (personally I never recommend to call external services from AL if you plan to be scalable and if you plan to have an high volume of transactions) and in these scenarios removing Basic Authentication can be a big problem. I think that the main scenario which Microsoft has to think is different. Only 3% of the customers and partners I work with have integrations to external services handled via AL code. This is very nice and easy to use, but unfortunately I think that it doesn’t solve the real integration problems. With Dynamics 365 Business Central Microsoft has introduced the new OAuth2 module, a new module that has the goal to provide OAuth support for connecting Business Central to external services via AL code. What’s the impact about that? Tremendous I think! The analysis on this topic on the same above customers and partners base says that 99% of them are using Basic Authentication on SaaS now and they’re absolutely not ready to support OAuth2. Please remember that for on-premises, Web Service Access Key (Basic Auth) will remain an option for the time being. Actual plans are to remove support for Basic Authentication on SaaS in 2022 Release Wave 1. The capability to access web services in Business Central using Web Service Access Key (Basic Auth) is deprecated for SaaS and OAuth2 will be the authentication option for SaaS. Microsoft is planning to not support anymore the Basic Authentication (username and web service access key) mechanism in the future. This is the most problematic topic I think. I know that this cannot be a very quick process, but you’ve one year to do so, so start accordingly. You should also start replacing your page-based web services with APIs (as said frequently on our lates webcasts).
WAVES CENTRAL UPDATE FAIL HOW TO
Here I’ve explained in the past how to use them. If you’re on this situation, you should work on this and start using OData V4 Unbound and OData V4 Bound actions. Lots of customers and partners have processes called from external clients that are codeunits exposed as SOAP endpoints. OData pages are totally replacing SOAP pages just now (at least on my cases). 85% of them are using Codeunit exposed as SOAP endpoints.
![waves central update fail waves central update fail](https://community.inovelli.com/uploads/default/original/2X/9/9249fb2f3b55306f97ec23b1ff0ddc2eac809461.png)