Re: [dotnetopenauth] Quickbooks and DNOA

[Andrew Arnott]

Hi Denethor,

It looks like you're off to a good start.  Authorizing requests to dynamically created URLs should be no problem at all.  Just wrap any URL in a MessageReceivingEndpoint and send it through ConsumerBase.PrepareAuthorizedRequest and you're good to go.

--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre

On Mon, Aug 20, 2012 at 4:54 AM, Denethor <kbelos...@gmail.com> wrote:

Hello everyone!

I need to query the Quickbooks REST services from the .NET 3.5 application, so I decided to use DNOA to OAuth-orize there.

To start, I downloaded the latest version package (4.1.0.12182 to be exact), opened the Samples solution, took a look around; and then added a QuickBooksConsumer, following the example of Google Consumer, changing urls as needed.

Now, here comes the problem that I face.

The QB services have the following urls:

https://services.intuit.com/sb/{0}/v2/{1}

where:

{0} is the name of the object to get records of (like, Invoices, Payments, Accounts &c.)

{1} is the realmId, or the Id of the company the user has OAuthorized the app to fetch the data for

So, when I need to make an authorized call to the QB services, I need a dynamic url that needs to get constructed first. However, it looks like this is not currently supported by DNOA; or at least I couldn't find it in the samples.

Can you give me a hand here and tell me if there is a way to pass dynamic urls when making authorized requests?

Thanks in advance!

--
You received this message because you are subscribed to the Google Groups "DotNetOpenAuth" group.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/to_my38sZigJ.
To post to this group, send email to dotnet...@googlegroups.com.
To unsubscribe from this group, send email to dotnetopenid...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dotnetopenid?hl=en.

[Denethor]

Indeed... for some reason I just overlook the possibility to create a new MessageReceivingEndpoint each time before calling PrepareAuthorizedRequest instead of using the single one as is done in Google sample. Stupid me!

Thank you very much for your help! :)