api - OAuth 2.0 two-legged authentication vs SSL/TLS -

i have 2 enterprise servers need communicate in secure way, , comparing using ssl (with client/server certs validate both sides) vs two-legged authentication using oauth 2.0 (optionally mac tokens or jwt tokens).

historically oauth seems have been created totally different purpose (the 3-legged case user allowing service access data somewhere), , although two-legged integrated oauth 2.0 spec, have seen two-legged oauth 2.0 doesn't seem offer additional protection on ssl.

the point can think of oauth potentially easier configure ssl, , easy make mistakes things accepting bad ssl certs can compromise security. not sure if reason enough go oauth.

note mention these separate options, think using oauth entail using on top of https/ssl, both used.

is there real advantage of using oauth 2.0 two-legged scheme server-to-server communication (no user involved)?

note: did find a similar post here, quite old don't feel gave satisfactory answer on matter.

i'll respond comment:

my question that, assuming using ssl proper client/server certs identify each machine, value using oauth (2 legged or similar) on top of authorize servers 1 (assuming there no user involved). – locksleyu

summary: wouldn't bother doing both.

details: 2-legged oauth secure consumer secret is. mutual auth ssl secure private key. assume you'll storing these in encrypted store on each server. both stored in same place see no additional security comes adding oauth.

now if considering choice between mutual auth ssl , standard ssl authentication, perhaps oauth can play role there. go whichever of options seems easier. if have oauth system in place , can add server auth it, perhaps that's way go. otherwise, go mutual auth ssl. tends bit of hassle configure works , once set up.