David Carney

You can apply ACLs to it, policies, all that kind of stuff.

You can build applications with that.

That's what Aperture is as well.

It's fundamentally a TSNet application.

So it just shows up as a service.

So

The nice thing about TSNet is that, yeah, you can turn any kind of service into effectively what appears to be a device.

And then you can apply rules in terms of who can access that with what level of permissions and all that kind of stuff.

In terms of just running TS-IDP as a service inside of your network?

Well, how does Proxmox be able to support TS-IDP?

It's just another OIDC endpoint.

Yeah, and we've added, I mean, there's OAuth 2.1 support or 2.0.

I mean, we brought it up to the almost OAuth 2.1 as the MCP spec was evolving last year.

And then we paused it a little bit.

But yeah, OADC, OAuth 2, it should just work.

Yeah.

One of the reasons we spent some time working on DS-IDP last year is because a lot of the existing IDPs, like the big ones out there, didn't support some of the things that MCP was calling for, like dynamic client registration, for instance.

So we built that into TS-IDP, so it effectively let us bolt on these missing capabilities.

So you can not only continue to use your existing external identity provider, but you can augment its capabilities with TS-IDP inside of your private network.

I was getting deeper and deeper into MCP last summer and definitely into the fall.