Web service security
Security is an important part of a solution involving web services. This is because the client calling the web service endpoint is likely not delivered by Microsoft and also because the interaction between the client and Business Central happens over a network.
This article provides recommendations that you can implement to make your web services applications secure.
For more general information about security in Business Central, see Security overview.
Web service authentication options
Here are some authentication options you can use:
- Authentication: Learn about the basic authentication methods for web services in Business Central.
- Authentication with OAuth: Use OAuth, an open standard that lets you authorize access to web services in Business Central online.
- Walkthrough: Creating a console application that uses OAuth: See an example of how to use OAuth in a console application.
- Service-to-service authentication: Use this method for scenarios where integrations need to run without any user interaction.
- Supported cipher suites in outgoing calls: Use an HTTPS certificate to connect to an external API from AL Httpclient.
- How to restrict network access from/to Business Central online: Use Azure security service tags to limit network access to and from Business Central online.
- Securing remote connections using certificates (on-premises): Learn how to use security certificates to help secure connections with Business Central (on-premises).
See also
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應