| ▲ | OptionOfT 2 hours ago | |||||||
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. | ||||||||
| ▲ | gopalv 44 minutes ago | parent [-] | |||||||
> Constrained Delegation This was pretty much Kerberos, but the embrace-extend Microsoft version was better than the regular krb5. AD was the only consistent implementation across deployments, because it was nearly identical across customers. Every linux implementation would be a unique snowflake you needed to know exactly how it worked each time, while the Microsoft version had quirks but it was the same issues in every customer (RBCD). | ||||||||
| ||||||||