I'm not sure what that means in this context. Why would you want to run as an oAuth service? You would authenticate users?

If you really need an oAuth server, there are products that provide this as a standalone. In the .NET Space there's Identity Server which provides a federated authentication solution for user management and which includes oAuth support.

I can't imagine you'd want this though. Setting up oAuth in an application is a pain, and typically if you do use it you want use a provider that everybody is using so you get the benefit of the single sign on. For a one off oAuth is way to much hassle (on both ends) to be worth it.

+++ Rick ---

Can it be done with Web Connection? Pretty sure it can. Is going to be easy? No... oAuth requires a bunch of low level message semantics, token creation and security related message encryption etc. which you would likely integrate via .NET (with wwDotnetBridge).

I don't know exactly what's involved but there's a reason why there are dedicated applications that provide that sort of functionality - it's not a small job to get this right, plus the specs are confusing with all the back and forth messaging. And even then it seems each oAuth implementation tends to be slightly different in naming and integration with other tools.

Possible perhaps, but probably not worth the time and effort to get it right.

+++ Rick ---