OAuth is just a matter of calling another endpoint with credentials and getting a bearer token that is valid for a certain time and injecting that into the headers of the actual request.
See this blog article Calling the Force.com REST API from BizTalk Server, now only available in the Internet Archive Way Back Machine, that detailed how to do it for Salesforce OAuth. Note that different systems have implemented OAuth slightly differently including whether to use basic auth initially, or to use a secret key to get the token. Also how the OAuth token expires can differ, some will only expire after a fixed time, whereas others will also expire a token whenever you request a new one. So you need to determine how the OAuth you are connecting to behaves and amend the code accordingly. You can initially just write a Class that you can call from a test class to get the OAuth part working, before you inject that into the WCF End Point Behaviour.
I've taken that OAuth behaviour and amended it so that it gets the password/secret from a SSO Affiliate Application rather than from the Send Port Configuration, also making the OAuth URL configurable, and have also created a copy with amendments for another systems which had different credential and token expiry requirements.
Update, same author published this Calling the Force.com REST API from BizTalk Server - Multiple Endpoints