logoalt Hacker News

The Active Directory Era Is Finally Over

51 points • by FinnLobsien • today at 2:15 PM • 23 comments • view on HN

Comments

OptionOfT • today at 5:48 PM

I remember in the past where we had users in AD, we'd sign in via ASP.NET, where we had to do something to allow that ASP.NET session to be elevated to one valid in Active Directory.

That session was then used to connect to Microsoft SQL Server where access to data was set at a company level.

It all flowed beautifully.

I remember having an issue with A user delegating to Service A which then delegated to Service B. That second hop is kinda special. Service A must be allowed to re-delegate.

(I quickly googled it) The solution was Constrained Delegation with Protocol Transition...

This brings back memories.

skinfaxi • today at 5:00 PM

> As an example, GitHub automation requires personal access tokens or GitHub private keys and doesn’t work with any directory identity.

Can't you create an Entra app/service principal and use OIDC to avoid personal identities?

sirjaz • today at 5:03 PM

The funny thing is that AD has all the capabilities that are discussed here. Even AWS recommends it for kubernetes as a service account using gmsa: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...

➕ show 1 reply
tarballing • today at 5:44 PM

This is an advertisement

JP44 • today at 5:02 PM

Unrelated but Infisical recently moved existing rbac features from their selfhosted version behind a paywall [1]. The discussion has had no response from the team in the past 2 days [2]

[1] https://www.reddit.com/r/homelab/s/teM83aKLMa [2] https://github.com/Infisical/infisical/discussions/9499

indigo945 • today at 5:05 PM

AI-generated blogspam. Also:

    > Human approval doesn’t scale to developers creating and deprecating testing 
    > databases, Kubernetes clusters, and CI runners at will. Contemporary AD 
    > implementations deal with this by deferring authority. An admin token (sometimes 
    > hardcoded…) automatically joins new identities. [...]
    > Even if you built all of the complex automations to reflect every testing database 
    > and Kubernetes pod in AD with automated admin approval, it’s security theater. The 
    > unified directory would exist on paper, but lack authority. [...]
    > Modern cloud infrastructure automatically asserts machine identity: [...] In 
    > Azure, you can configure a machine identity in Entra ID and let Azure’s Instance 
    > Metadata Service (IMDS) automatically issue OAuth tokens when machines request 
    > them.
Okay, so configuring machine identities manually in AD doesn't "scale" to the container age, fine. But configuring machine identities in EntraID does? How is auto-issueing identities in AD "security theater", but auto-issueing identities in EntraID the way to go?
exabrial • today at 5:41 PM

Yeah but it kind of sucks.

Instead, we have 20 passwords for 25 different internal dev tools. We have to pay $2.99/month to some "MDM" that barely has control of the machine.

AD was good in theory, but the weight of crap implementation that had to be preserved for backwards compatibility was awful. It was like IE6 unfortunately.

Kerberos is a really good concept. That should be what we're doing instead of paying $2.99/month*mac for management.

15o9o • today at 5:02 PM

anyone remember https://en.wikipedia.org/wiki/Bitium ? Now google cloud identity.

whalesalad • today at 5:08 PM

AD = LDAP, Kerberos, DNS and user/group/host policy. That is not really ever going away. Particularly for on-prem large institutions with lots of machines. In BYOD environments sure but I don't think that has supplanted your traditional company issued Lenovo/HP/Dell in the majority of institutions.

➕ show 2 replies
br0ceph • today at 5:09 PM

AD is the worst, its the MS moat, to lock all into their vendor garbage.

I tell ppl all the time, AD is an infection, and wherever u see it, it must be eliminated.

Microsoft has never built any secure software ever or had its customers in mind, so putting AD at the center of ur organization and allowing it to fester, is not doing the needful

Avoid microsoft at all costs, or ur just clownstriking urself

➕ show 1 reply