Weird implementation of oAuth 1

See more:

OAuth

Im currently working with an Indian developer and he's holding on to an oAuth implementation that I haven't seen before. I don't think this is the right way of doing it but who knows. All I know that when I did a oauth integration for a xero partner app there were a lot more things involved.

Can anyone tell me whether this makes sense?

Me: What are the urls for RequestToken, AccessToken, etc?
Other dev: No Token required.

Me: What is the consumer key? You only gave me the consumer secret.
Other dev: It will be the public key you will define. That key will get sent in header. I will use your public key ( consumer key ) and our secret key to encrypt back to the signature you will send me in the header.