The "shared secret" property is only used by functions of the API that require authentication. Simple functions like getting public photo info do not require authentication, and not being required to enter the "shared secret" would make it easier to use this module for simple tasks.

Comments

drewish’s picture

drewish commented

personally i don't really think it's that big of a burden to copy and paste one extra line. you've got to setup the key either way and it's right there when you're copying the key.

Robbie Sternenberg’s picture

Robbie Sternenberg commented

The code is already set up in the rest of the module for it to be optional. Don't see why it should be required in the settings form if the username isn't.

Anonymous’s picture

Anonymous (not verified) commented

ill look into this, thanks

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed

Will come back to this after we have released a 1.0 official version of this module

Anonymous’s picture

Anonymous (not verified) commented
Title: Make "shared secret" field optional » [PRIORITY 1] Make "shared secret" field optional
Version: 5.x-1.3 » 6.x-1.x-dev
Assigned: Unassigned »
Status: Postponed » Active
Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

We can probably take out this field but for the meantime at least the "shared secret" field has been disabled.

I'll get this committed to the development branch later today

Best,
Paul Booker
Appcoast

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.