When I use the HTTP OAuth2.0 connector and I try to set up authentication, I use the redirect URI in the Fusion 2.0 documentation but when it redirects it says page not found. Do I have the wrong redirect?

Hi Caden,

I think you have identified a problem with our documentation. We will work with our team to fix. In the mean time, the correct redirect URI is: https://app.workfrontfusion.com/oauth/cb/oauth2

Apologies for the likely confusion that would cause.

Hi Caden, I'm glad that got you a bit further.

A 403 error is most commonly associated with a concept wherein you don't have the appropriate permissions in the 3rd party system (or haven't requested them and got them granted in an fully fledge oAuth2 implementation).

This will definitely be nuanced based upon each 3rd party API, but it does indicate that "authentication" worked...but "authorization" did not .

To your question on the header, the default is that our HTTP connector will send the token in the header (but you can change that with advanced settings of the HTTP connection).

Out of curiosity, what service are you connecting to?

For what it's worth (to anyone else our there:) ). Caden an I were able to connect and successfully establish an HTTP oAuth2.0 connection to Bluescape in Fusion. It turns out, once you get all the URIs right (from 3rd party systems), Fusion does a good job of handling the rest. A few notes for others that may be worthwhile.

The HTTP OAuth2 connection follows a standard "Authorization Code Flow" or "Implicit Flow". (you choose which one). These are oAuth 2 standards and a good resource to learn more about those standards is here. As such, step one is to ascertain what type of flow the 3rd party uses and how closely they follow the standard.

In the case of an "Authorization Code Flow", Fusion automatically passes in the standard parameters for the GET to the authorization endpoint (e.g. client_id, redirect_uri, response_type, etc.). You don't have to add these in yourself. If there are "non-standard parameters", then you can add those as well. Once the authorization part is completed, it will automatically pass standard parameters for the POST against the Token Endpoint (e.g. grant_type, code, redirect_uri, etc.).

In other words, many times (and this time), all we had to do is enter the correct Authorize URI, Token URI, client_id, and client_secret and everything else just works.

Cheers.

@Darin Patterson - inactive‚ Glad I found this post noting that the redirect is https://app.workfrontfusion.com/oauth/cb/oauth2 - as I was working with the https://www.workfront.com/oauth/cb/oauth2 uri which is still referenced in documentation - here. There did not seem to be any 'straight' OAuth2.0 instructions, just those for MS & Google.

Unfortunately while I now can get past the 404 error and see the code returned in the pop-up window I am getting a Failed to verify the connection error. But no error codes or anything showing in Fusion Dev Tools that I can see. Wonder if anyone has managed to connect to GoToWebinar via OAuth before? Have it working in OK in Postman......