I have been writing a bunch of small samples apps, trying to improve my understanding of volatility-based decomposition solutions. As part of this effort, I needed a proxy to link calls to services without the client directly calling the services. This is a fundamental detail in any microservice implementation and there are libraries to enable this, if I where building Service Fabric applications. But that isn’t what I am trying to do. I need a tool that is light-weight, super-easy to use, and something that at least vaguely follows the SF communication patterns. Continue reading Yet Another Service Locator
I have been working on a POC for injecting bulk entitlements into our Access Management System. I guess you could think of our system as a big loop. Entitlements are created in the AMS. Users request an entitlement, which kicks off a workflow. Once the entitlement is approved, it flows into AD. The part I have been noodling around with is reading the permission out of AD.
I’ve been playing with this for years, literally. I wrote some simple code a few years back. For this POC, I dusted it off and showed it around. I still had to migrate the code into the POC solution, so I had a chance to clean it up a bit. No problem. My old code uses UserPrincipals to pull the data out of AD.
var ctx = new PrincipalContext(ContextType.Domain);
var userPrincipal = await Task<UserPrincipal>.Factory.StartNew(() => UserPrincipal.FindByIdentity(ctx, request.UserId)) ?? new UserPrincipal(ctx);
response.User = userPrincipal.Convert();
It can be a bit slow. At least the first query is slow. It gets faster after the spin up. Still… I think I can make it better.
After poking around for a bit, I found the information I needed to access the AD container via LDAP. Amazingly enough, the security team posted all of the needed info on the internal Wiki. I’m not going to go into too much detail because I don’t really want to share any details about our network.
Anyway, once I pulled the data, I needed to parse the data into something I could use for my POC. I looked around online and I could not find a single reference that showed a complete RegEx sample. I saw some fragments, but nothing complete. So here is what I came up with…
var regex = new Regex($@”CN=(?<CN>[\w –]+)(,OU=(?<OU>\w+( \w+)*))+(,DC=(?<DC>\w+))+“);
That’s it. I only need the “CN” portion of the string but I thought I’d parse everything for future use.
PS: I’ll fix the broken images when I have a chance.
I’m building up a sample app that leverages the MahApps.Metro libraries. One of the challenges is setting the AppTheme and Accent colors dynamically. I looked through more than a few online solutions and none of them worked for me. Usually, the syntax was from an earlier version and didn’t match the ThemeManager object that I downloaded from NuGet (v126.96.36.199).
After comparing the sample app (v4.5) against my code in VS, I noticed the results from ThemeManager.DetectAppStyle() was always null in my app and valid in the sample app. Continue reading Setting Theme/Accent with MahApps.Metro
I have three different projects converging. They all need a more feature rich base class in the business layer.
I haven’t settled on a name for this base class. EntityBase? BusinessBase? BusinessObject? I expect something will stick in the near future.
You should notice that most of these interfaces are pre-existing Microsoft interfaces. ISupportUndo and ITrackStatus are inspired by Rockford Lhotka’s CSLA framework. The details are changed, but I really like the syntax to make the interface more readable. “I support undo.” I can’t think of a better way to express what the interface does. Can you?
I’m still working on the implementation details. I’ll share more once I have a stable sample app.