Now that you have your development environment set up, you’ll explore the structure of a Blazor project and learn how to add new pages.
Razor is a markup syntax that uses HTML and C# for writing UI components of Blazor web apps.
Razor is based on ASP.NET and designed for creating web apps. Continue reading “What is Blazor Components ?”
Now that you’ve configured the certificates for eCommerce Web Application Gateway and the backend pool, you can create a listener to handle incoming requests. The listener will wait for messages, decrypt them by using the private key, and then route these messages to the backend pool.
In this unit, you’ll set up the listener with port 443 and with the SSL certificate that you created in the first exercise. The following image highlights the elements you’ll set up in this exercise.
Diagram that highlights the elements (frontend port, SSL certificate for eCommerce Web Application Gateway, listener, and rule) created in this exercise. Continue reading “Modern eCommerce Web Application encryption”
You have configured SSL for the connection between Azure Cloud Application Gateway and the servers in the backend pool. For the shipping portal, you need full end-to-end encryption. To do this, you’ll also need to encrypt the messages that the client sends to Application Gateway.
Application Gateway receives requests through one or more ports. If you’re communicating with the gateway over HTTPS, you should configure an SSL port. Traditionally, HTTPS uses port 443. Use the az network application-gateway frontend-port create command to create a new frontend port. The following example shows how to create a frontend port for port 443: Continue reading “How to Configure an Web Application Gateway listener for encryption”
You want to implement end-to-end encryption for the shipping portal application. Encrypting all data between users and servers will help ensure that no unauthorized user can intercept and read the data.
In this unit, you’ll set up the web application and the application gateway. Next, you’ll create some self-signed SSL certificates and enable encryption in your backend pool to help secure the traffic from the application gateway to your servers.
The following image highlights the elements you’ll configure in this exercise. You’ll be setting up an application gateway by using Azure Application Gateway v2.
Continue reading “How to implement end-to-end encryption for the shipping portal application”
The back-end pool contains the servers that implement the application. Azure Application Gateway routes requests to these servers, and can load balance the traffic across these servers.
In the shipping portal, the application servers in the back-end pool must use SSL to encrypt the data that passes between Application Gateway and the servers in the back-end pool. Application Gateway uses an SSL certificate with a public key to encrypt the data. The servers use the corresponding private key to decrypt the data as it’s received. In this unit, you’ll see how to create the back-end pool and install the necessary certificates in Application Gateway to help protect the messages that are transmitted to and from the back-end pool. Continue reading “Web Application Cloud Configure back-end pools for encryption”
Encrypting your data while it’s in transit is an important step toward securing your applications. You can purchase certificates from a certificate authority and use them to encrypt the messages that pass in and out of your servers. This prevents unauthorized users from intercepting and examining the information in these messages while they’re being transmitted.
In the shipping portal, encryption is important because we’re dealing with shipping customer orders. If someone can access the transmitted data, they can view sensitive information, such as customer details or financial account data. Continue reading “How does Web Application Gateway and encryption Work ?”
Companies that build web apps commonly hire developers for different roles. Some developers create back-end, server-side logic. Others build client-side web apps. These developers often use different development languages and technologies.
C# and Microsoft .NET are popular choices for building server-side logic. But client-side apps are often built with web UI frameworks, which commonly use JavaScript. The use of multiple languages and toolsets requires multiple sets of skills and often requires two separate teams. Also, code to transfer and represent data must be built in both languages and kept in sync. Continue reading “What is Blazor Web Framework? – Build a web app with Blazor”