API Authentification resulting in 403 Forbidden

  • Resolved speckmann

    (@speckmann)


    9 months, 1 week ago

    Dear support team,

    • we would like to use the API Integration.
    • The integration without Authentification works as expected -> message: “Cache Cleared”
    • When we activate the authentification we get a 403 forbidden “Access Denied”
    • The url format: https://{ourdomain}.de/wp-json/breeze/v1/clear-all-cache?key={ourpassword}
    • We tried different keys
    • We also tried adding a basic auth using an application password -> also no effect.

    Are we missing anything in the setup?

    Thanks a lot in advance and best,

    Christoph

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author owaisalam

    (@owaisalam)

    9 months ago

    Hi,
    This issue usually happens when the key you’re passing does not match the Authentication field. Please try refreshing the secret key by using the “Refresh Key” option, save the changes, and then apply the new key.

    Thread Starter speckmann

    (@speckmann)

    9 months ago

    Hey owaisalam,

    I reset the key and I still get the result “Access Denied”.

    Furthermore, I checked the stored values in the database:

    • There is on breeze-api-token stored in the breeze_advanced_settings, which is the value shown in the frontend
    • in the breeze_file_settings option there is also a breeze-api-token set to a different value.
    • I tested this value and my request works.
    • Can I delete the breeze-api-token from the breeze_file_settings?

    Best,

    Christoph

    Plugin Author owaisalam

    (@owaisalam)

    9 months ago

    Please make sure that the Authentication code value is the same in both places:

    • The Authentication field inside the Breeze settings.
    • The value stored in the breeze-config file.

    If both values match, the feature should work correctly.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘API Authentification resulting in 403 Forbidden’ is closed to new replies.