Setting up config.yml for CMS connection to Bitbucket

Is this correct for the config.yml file?

backend:
name: bitbucket
repo: drewbacca48/one-click-hugo-cms

Hi @drewbacca49, it should have proper indentation:

backend:
  name: bitbucket
  repo: drewbacca48/one-click-hugo-cms
1 Like

I was curious if this callback url is correct?

backend:
name: bitbucket
repo: drewbacca48/one-click-hugo-cms
branch: default (can this be set to master?)
auth_type: implicit (is there another option so this does not expire in 1 hour?)

Sorry @drewbacca49, I missed on your response.
There are two ways to authenticate with Bitbucket:

  1. Using OAuth authorisation code grant which requires a backend. Netlify can facilitate the backend for you.
    You can configure it by following the first section of the docs here: https://www.netlifycms.org/docs/bitbucket-backend/ which in turn will direct you to the Netlify docs here https://docs.netlify.com/visitor-access/oauth-provider-tokens/#using-an-authentication-provider to create the backend mechanism via Netlify.
  2. Using an Implicit grant which doesn’t require any kind of backend service. You can configure it by following the docs here: https://www.netlifycms.org/docs/bitbucket-backend/#client-side-implicit-grant-bitbucketwhich which in turn will direct you to the Bitbucket docs here: https://confluence.atlassian.com/bitbucket/oauth-on-bitbucket-cloud-238027431.html.

The 1 hour expiry is indeed an issue (when using the second method), but the CMS will try to refresh the token silently when it see it expires.

When using the first method the callback in your screenshot is correct.
Which method are you trying to set up?
Thanks and sorry again for the late reply.