Simple 3 Steps Docker Window Containerize .Net Hello World

 

Prerequisites 

Azure Kubernetes Services Fundamentals

Introduction

Kubernetes is an open source where one can automate deployment, scale the application system and manage containers.

Sitecore Azure AD B2C User.Identity.IsAuthenticated is false Set AuthenticationManager

 

Solution to use ExternalLoginCallBack

Sitecore exposes /identity/externallogincallback URL which basically invokes the HandleLoginLink processor whose primary responsibility is to transfer the AspNet.ExternalCookie issued by OIDC in to final AspNet.Cookies authentication token. The sitecore virtual users then get created and session is initialized. Therefore we must include the above end point as our callback end point. Once this callback is triggered, it will redirect the user to returnUrl specified.

https://stackoverflow.com/questions/29907155/external-cookie-for-external-login-in-asp-net-owin

https://blog.baslijten.com/federated-authentication-in-sitecore-error-unsuccessful-login-with-external-provider

Technically this is what it does behind the scene- This is just a hack , don't use this. Refer above code snippet to redirect to Sitecore external call back to get away with External Cookie reference.

Azure AD B2C Overview

App Registrations

• Register your application in Azure AD B2C. 
• Create new application ID or client ID that identifies your application.

Select Identity Provider

• Facebook
• Twitter
• Google
• Amazon
• MS
• Github
• Local account

Select Policy

• User flow- User sign up /sign in, reset , Change password etc.
• Under user flow- select token claims

What is claim is a variable or attributes of logged in person- return user details post login

Claim: 

• Display name
• Email
• Country
• Job Title
• Postcode
• City
• USER OBJECT
• Identity provider

Scale up Scale down vs Scale In Scale Out

 

Scale In /Out	Scale Up/Down
Downtime: No downtime when provisioning in cloud	Downtime to some extent as there will be migration of code and configuration. No downtime when scaling process happens however migration of code configuration kicks off post scaling results in downtime.
Scenario: When code is alright, however no of users during the peak increases and server is unable to serve request. Increase no of boxes or instance to distribute loads of users across . Load balancing of users or distribution of users to serve request.	Scenario : When bad code or design leads to more CPU and memory utilizations. Need to increase server capacity
No sticky session Out proc session	In Proc session or state server session will do.

Kubernetes 101 Know how

Clusters| Nodes| Pods| Helm

Node := Master Node + No. of Worker Nodes

Analogy: Cluster is like a train and Nodes are just like a compartment 

Kubernetes clusters are comprised of one master node and a number of worker nodes. These nodes can either be physical computers or virtual machines, depending on the cluster. The master node controls the state of the cluster; for example, which applications are running and their corresponding container images. 

How many clusters are in Kubernetes?

25 supports clusters with up to 5000 nodes. More specifically, Kubernetes is designed to accommodate configurations that meet all of the following criteria: No more than 110 pods per node. No more than 5000 nodes

What are pods and clusters in Kubernetes?

A Kubernetes cluster consists of a set of worker machines, called nodes, that run containerized applications. Every cluster has at least one worker node. The worker node(s) host the Pods that are the components of the application workload. The control plane manages the worker nodes and the Pods in the cluster.

Helm is a Kubernetes deployment tool for automating creation, packaging, configuration, and deployment of applications and services to Kubernetes clusters. Kubernetes is a powerful container-orchestration system for application deployment

Content Security Policy CSP In or Out

Content Security Policy Script-src is something that tech lead or developer might have come across . This is one of the most common low security vulnerability defect raised by external penetration tester. They might suggest to whitelist Js library or third party libraries to safe guard against XSS attack. 

CSP protect from XSS

Well if you are working on .Net the only option you have is to add custom response header in Web.config file and list all JS. But here is the catch if you working with third party analytics this become tricky. There is a constraint and challenge to do so. Per say, these analytics injects lot of js libraries at runtime. It can be facebook , google tag manager, live person, social media plugins or advert. This is where one needs to draw line and give business technical reason why this cannot be achieved. Next stuff is browser compatibility. Under the hood testing will become exhaustive and chances are these are prones to more defects that leads to unknowns while move to production. Next time you come across CSP , think twice do your thorough research before you commit something. 

Sitecore XM Cloud Troubleshooting Part 2 Remote name could not be resolved 'dist.nuget.org'

Remote name could not be resolved 'dist.nuget.org'

Solution

Next, set the Interface Metric to 1 for Wi-Fi

Set-NetIPInterface -InterfaceAlias 'Wi-Fi' -InterfaceMetric 1

https://sitecore.stackexchange.com/questions/26095/remote-name-could-not-be-resolved-dist-nuget-org

 

Sitecore XM Cloud Deep Dive Troubleshooting Part 1

 I started with Github repo and followed the step. I got error while running the step given below

Bring up all the application elememnts for Local Mode

Next, use the up.ps1 script to bring up all of the containers required for Local Mode.

.\up.ps1

ERROR

a Windows version 10.0.20348-based image is incompatible with a 10.0.19042 host

I refer version of docker 

https://hub.docker.com/_/microsoft-dotnet-sdk

Go to .env file and change this configuration 

FROM

NETCORE_BUILD_IMAGE=mcr.microsoft.com/dotnet/sdk:6.0-nanoserver-ltsc2022
NETCORE_RELEASE_IMAGE= mcr.microsoft.com/dotnet/aspnet:6.0-nanoserver-ltsc2022

TO

NETCORE_BUILD_IMAGE=mcr.microsoft.com/dotnet/sdk:6.0.400-nanoserver-1809
NETCORE_RELEASE_IMAGE= mcr.microsoft.com/dotnet/aspnet:6.0.400-nanoserver-1809

C# Expression bodied Method reduce lines of code

Friendly reminder about C# expression-bodied methods 🙂🙏 #dotnet pic.twitter.com/XnUAnmOdQr

— Dan Clarke 🎙 (@dracan) July 19, 2022

C#: String.IsNullOrEmpty vs String.IsNullOrWhiteSpace

C#: String.IsNullOrEmpty vs String.IsNullOrWhiteSpace

🌊 C#: String.IsNullOrEmpty vs String.IsNullOrWhiteSpace 🌊

What happens to your validation if the user enters a string like " "? That string is made of white spaces, so it is not empty.

Consider using IsNullOrWhiteSpace when validating inputs!#csharp #dotnet pic.twitter.com/s7jSsjCHlh

— Davide Bellone 🐧 (@BelloneDavide) July 20, 2022

Best Practice Csharp Use NameOf for Constant

#100DaysOfCode
Csharp Best practice - Const pic.twitter.com/bESVIrbfR3

— san (@santoshpoojari3) August 19, 2021

Productivity Tool MSBUILDLog and Project

Download https://msbuildlog.com/

Visual Studio Build Log Extension

Tools to make working with the Visual Studio project system for C#, Visual Basic, and F# easier. This extension is for VS2017 and VS2019. Search the extension marketplace if you require a different version. Build logging A tool window is added under View > Other Windows > Build Logging. The window allows logging both regular and design-time builds in the project system. See the docs for more information.

https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools

Hello world Csharp

Next time you write Hello World! Do this,

using static System.Console;

public class Program {

static void main() => WriteLine("Hello World");

}

 

Csharp Interface with same method implementation

Clean Code Exception Filters in c#

 

Clean code always looks like it was written by someone who cares.”

― Robert C. Martin, Uncle Bob

C# Exception filters has been around since advent of C# 6.0 , I'm sure we rarely use it because we are so used to old way of using conditional exception handling.

Cut to the chase........!

Run dotnet in browser

https://try.dot.net/

Happy Coding!

Azure Storage Message Queue Topic & Service Bus

 

Azure Managed Identities- System Identity vs User Assigned Identity

 

Managed Identities

Managed Identities are in essence 100% identical in functionality and use case than Service Principals. In fact, they are actually Service Principals.

What makes them different though, is: – They are always linked to an Azure Resource, not to an application or 3rd party connector – They are automatically created for you, including the credentials; big benefit here is that no one knows the credentials

Managed Identities exist in 2 formats: – System assigned; in this scenario, the identity is linked to a single Azure Resource, eg a Virtual Machine, a Logic App, a Storage Account, Web App, Function,… so almost anything. Next, they also “live” with the Azure Resource, which means they get deleted when the Azure Resource gets deleted. – User Assigned Managed Identity, which means that you first have to create it as a stand-alone Azure resource by itself, after which it can be linked to multiple Azure Resources. An example here could be out of an integration with Key Vault, where different Workload services belonging to the same application stack, need to read out information from Key Vault. In this case, one could create a “read KV” Managed Identity, and link it to the web app, storage account, function, logic app,… all belonging to the same application architecture.

Let’s walk through a quick demo scenario for both, using a Virtual Machine as Azure Resource:

• From the Azure Portal, select the Virtual Machine; under settings, find Identity
• Set Status as On, and save the changes

Switching to Azure Key Vault / Access Policies, we can now define this System Assigned Managed Identity having get and list permissions (or any other) for keys, secrets or certificates. For example reading out an Azure Storage Account Access key or similar.

Notice how Azure Key Vault is expecting a Service Principal object here (where in reality we are using a Managed Identity).

Similarly, let’s remove the System Assigned MI of the VM and use a User Assigned one in the next example (an Azure Resource can only be linked to one or the other, not both…):

• From the Azure Virtual Machine blade, navigate to Identity and switch the “Status” toggle button to Off.
• This will prompt for your confirmation when saving the settings

As you notice, the Managed Identity object gets immediately removed from Azure AD. Yes, security is key here…

• Wait for the deregistration of the object.

Remember that a User Assigned Managed Identity is a stand-alone Azure Resource, which needs to be created first, after which you can assign it to another Azure Resource (our VM in this scenario).

• From the Azure Portal, Create new Resource, and search for “User Assigned Managed Identity”

• click Create.
• Specify the Resource Group, Azure Region and Name for this resource.

• Confirm by clicking create and Wait for the resource creation to complete successfully.
• Once created, switch back to the Azure Virtual Machine, select Identity and select User Assigned
• Notice the Managed Identity you just created.

• Select it and add it as a Virtual Machine User Assigned object.

• Select another Azure Resource in your subscription, for example an Azure Web App, Logic App,… and once more select Identity from the settings. Below screenshot shows what it looks like for an Azure Web App Resource:

To complete the sample scenario, let’s go back to Azure Key Vault, and specify another Access Policy for this User Assigned Managed Identity:

• Select your Azure Key Vault resource, followed by selecting Access Policy from the settings.
• Specify the Key and/or Secret Permissions (for example get, list)
• Click “Select Principal” and search for the User Assigned Managed Identity you created earlier

After saving the changes, the result is that now both the Azure Virtual Machine as well as the Web App – having the User Assigned Managed Identity assigned to them – can read our keys and secrets from Azure Key Vault.

Summary

In this post, I wanted to clarify the use case, difference and similarities between Service Principals and Managed Identities. A Service Principal could be looked at as similar to a service account-alike in a more traditional on-premises application or service scenario. Managed Identities are used for “linking” a Service Principal security object to an Azure Resource like a Virtual Machine, Web App, Logic App or similar. For a 1:1 relation between both, you would use a System Assigned, where for a 1:multi relation, you would use a User Assigned Managed Identity.

Technical Architect B2B and B2C Authentication , Authorization and Access Policy

 

Azure messaging services - Event Grid, Event Hubs, and Service Bus

 

Comparison of services

COMPARISON OF SERVICES

Service	Purpose	Type	When to use
Event Grid	Reactive programming	Event distribution (discrete)	React to status changes
Event Hubs	Big data pipeline	Event streaming (series)	Telemetry and distributed data streaming
Service Bus	High-value enterprise messaging	Message	Order processing and financial transactions