Saving plugin settings killing AWS credentials?

  • Resolved orangeaxis

    (@orangeaxis)


    7 years, 11 months ago

    I have successfully set up Polly on my website (months ago), and am trying to set it up for a client of mine. I can get everything working but when I click “Save” on the plugin settings page, all of the field states return to “Please verify your AWS Credentials are accurate.”

    Steps:

    – Install and activate plugin
    – Create new IAM user with programatic access
    – Attach existing policies directly (PollyForWordpressPolicy)
    – Copy AWS keys and insert in plugin settings

    So far so good, now all of the plugin settings are editable. But as soon as I change a setting and save, all of the field states return to “Please verify your AWS Credentials are accurate.”

    Notes:

    – WordPress and all plugins are up-to-date
    – Cache was flushed before and after installation
    – Client is on GoDaddy
    – Client does not have a SSL cert

    Help?!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor tstachlewski

    (@tstachlewski)

    7 years, 11 months ago

    Hi @orangeaxis,
    Just to make sure, you wrote: “all of the field states return to “Please verify your AWS Credentials are accurate.” – does it mean that before (after you have initially provided credentials), those settings options were editable? And just then, after you modify some of them, they return to ‘Please verify…’ value? Or then were never in editable state?

    Cheers,

    Thread Starter orangeaxis

    (@orangeaxis)

    7 years, 11 months ago

    @tstachlewski yes that is correct. I can change the value(s) and all of the drop-down boxes work, but when I save, all of the fields return to “Please verify your AWS Credentials are accurate.”

    It sure sounds like a caching issue to me. Continuing to troubleshoot on my end.

    Thx!

    Thread Starter orangeaxis

    (@orangeaxis)

    7 years, 11 months ago

    I believe I have found the culprit. The Dashlane Chrome extension (Dashlane is a password manager) is looking at the AWS secret key textbox and considering it a password field. Dashlane was overwriting the AWS key with something else (probably the website WordPress admin password) every time I hit the settings page.

    Once I disabled the extension, I was able to get things working.

    Dashlane users – I would advise that you do *not* save if prompted by Dashlane once you enter your AWS keys.

    Thanks!

    Thread Starter orangeaxis

    (@orangeaxis)

    7 years, 11 months ago

    Resolved. 🙂

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

The topic ‘Saving plugin settings killing AWS credentials?’ is closed to new replies.