Actors Referencing .NET Standard ‘Works On My Machine’

So the age old ‘works on my machine’ is back at it again with Service Fabric Reliable Actors and likely Reliable Services in general (Stateless or Stateful). As you can see from the status my local dev cluster is reporting ‘it works on my machine’. I should be done right? 😊 I have been trying … Continue reading Actors Referencing .NET Standard ‘Works On My Machine’

Advertisements

Deploying to Standalone Cluster: FileNotFoundException

In my previous post, I demonstrated how I overcame some remote connectivity challenges that were preventing me from accessing my Service Fabric Cluster via PowerShell from other machines on my local network. Since then I have been able to deploy to my Standalone cluster using Visual Studio tools. Error event: SourceId='System.Hosting', Property='CodePackageActivation:Code:EntryPoint'. There was an … Continue reading Deploying to Standalone Cluster: FileNotFoundException

Standalone Service Fabric PowerShell Remote Connectivity Challenges with DevCluster

So after I got my Standalone Service Fabric Cluster setup and working I decided the Unsecure template wasn’t good enough and I wanted to try my hand at the x509 template. I went through the entire process (I’ll post on that later) however I was unable to access the Service Fabric Administration Console nor was … Continue reading Standalone Service Fabric PowerShell Remote Connectivity Challenges with DevCluster

Attaching the Bearer Token to Claims Identity in ASP.NET Core to implement On-Behalf-Of Flow

When you setup an ASP.NET Core web API project and go through the wizard to associate it with an Azure Active Directory tenant it will add the necessary plumbing within your project to get it all working. However, if you are ever in a place where you need to use on-behalf-of flow to obtain another … Continue reading Attaching the Bearer Token to Claims Identity in ASP.NET Core to implement On-Behalf-Of Flow

Azure AD B2C Error Code: AADSTS50011 Tip: Don’t botch the Reply Address

Application ID ‘c8f9a6ef-a5c6-4d19-993d-2c4ded2b55d6’ is a Web app / API. AADSTS50011: The reply address 'https://localhost:44318/' does not match the reply addresses configured for the application: 'c8f9a6ef-a5c6-4d19-993d-2c4ded2b55d6'. Do not get reply URL confused with home page URL. There is a dedicated place for Reply URLs and you can have more than one!

Azure Active Directory B2C Global Administrator can’t login to B2C tenant app

I have been doing some testing with the Azure Active Directory Graph API and encountered some issues when using my global administrator account to attempt login to one of the application’s I registered within the B2C tenant. In doing so, I discovered something interesting about the Global Administrator accounts within the Azure AD B2C tenant. … Continue reading Azure Active Directory B2C Global Administrator can’t login to B2C tenant app

Setting up and Managing Azure Active Directory B2C: The Complete Guide to Azure Portal Weirdness

So I’ve been working a lot with Azure Active Directory B2C recently and thought I would jot down some of the idiosyncrasies I’ve found while using the Azure Portal. The implementation leaves much to be desired and can be very jarring and seem disjointed to new users. I’ll focus on a few of the common … Continue reading Setting up and Managing Azure Active Directory B2C: The Complete Guide to Azure Portal Weirdness

AspNetCore.TestHost + Azure Active Directory (Part II)

So in my last post on the topic, I was describing some challenges I faced when receiving 401 not authorized errors when attempting to pass a seemingly correct bearer token to my Azure Active Directory protected WebAPI. I’ve discovered the solution. Not only was I able to get it working but it also works flawlessly … Continue reading AspNetCore.TestHost + Azure Active Directory (Part II)