Unable to get access token for SmugMug API (OAuth1.0a)

Questions
1

Describe the issue/error/question

Hi,

I’m running into trouble while trying to connect to SmugMug’s API using OAuth1.0a.

Authorization with SmugMug seems to work up to the point of redirection, but after the redirect the popup window shows the following response:

{"code":0,"message":"Unable to get access tokens!","hint":""}

Information on your n8n setup

  • n8n version: 0.174.0
  • Database you’re using (default: SQLite): MySQL
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
2

Hey @gnl, welcome to the community and I’m sorry to hear you’re having trouble with the authentication against this particular API. I could reproduce this and shall add this to our internal bug tracker for a closer look

4

Much appreciated, thanks! We’ve been otherwise very much enjoying n8n.

5

I’m getting the same exact issue with SmugMug API

6

Did anyone figure out a fix for this particular issue of connecting to Smugmug via OAuth1.0a? Years later and I still haven’t been able to figure out a fix.

Here’s the error that display when Smugmug sends me to the callback URL:

Error: Insufficient parameters for OAuth1 callback.

Received following query parameters: {“oauth_token”:“nCmjjvvqWNPM97S9VxGRf3KDsJwRf6r9”,“oauth_verifier”:“326828”}

Failed to connect. The window can be closed now.

7

You may have figure this out already in the time between November and April, but if not, I have a potential suggestion:

A common reason for this “insufficient parameters” error in OAuth 1.0a is that the application (in this case, your n8n workflow) is missing the original oauth_token_secret that corresponds to the received oauth_token.

When SmugMug calls back to your n8n workflow, it only provides the oauth_token and oauth_verifier. Your n8n workflow needs to have stored or be able to retrieve the original oauth_token_secret obtained in the very first step (Request Token step) to successfully exchange these temporary credentials for a permanent access token.

I came across this thread while researching how to enable SmugMug in an n8n workflow, so in case others find the same thread, I wanted to include this note. I’ll confirm once I’ve built my workflow but in case you see this and it was another issue unrelated to retaining the original token secret, please advise so I can update this suggestion.