-
Notifications
You must be signed in to change notification settings - Fork 975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth-ready ? #11
Comments
Have you tried passing the oAuth token as the SessionId? I will take a look at this at the weekend. Do you have any sample code I can test it with? It's very cool btw! |
Did you have any joy passing the oAuth token in the SessionId, I'm reasonably confident this might work?!? |
Hi Andrew, Can you just share the sample code using Oauth. Thanks in advance. |
I don't have an oAuth example in Apex myself, but i am sure if you search/ask on StackExchange there will be one. |
It would be a good blog post idea though, so i'll add it to my list of ideas! |
Hi Andy,
I explored adding OAuth compatibility : getting an OAuth token is easy enough, as well as initialising the InputHttpHeader on the MetadataService.
However, for some reason, WebServiceCallout.invoke insists on using the SessionId in the SessionHeader : have you any reason why ?
Any other idea about making apex-mdapi OAuth-compatible ?
Regards,
Rupert
The text was updated successfully, but these errors were encountered: