[Unecrypted password API call]

1 hour ago, jd6strings said:

THANK YOU!!! 

One last question...

I'm attempting to get the client autodebit settings from the API and I'm using the getSetting($client_id, $key) method.  It seems to be returning all the settings including those that are inherited.  I would expect that it would return the value for autodebit only if I'm passing that in as the $key parameter.  Is this not the case?

Thanks again for the great support!  I love Blesta and I am disappointed that I am forced to migrate away to a less user friendly platform...

Disregard!  I figured it out!

[Unecrypted password API call]

On 7/3/2017 at 5:45 PM, Tyson said:

Credits aren't stored, they're derived from the transactions that exist on a client's account that have not yet been applied to an invoice. You can fetch them via the API Transactions::getCredits.

THANK YOU!!! 

One last question...

I'm attempting to get the client autodebit settings from the API and I'm using the getSetting($client_id, $key) method.  It seems to be returning all the settings including those that are inherited.  I would expect that it would return the value for autodebit only if I'm passing that in as the $key parameter.  Is this not the case?

Thanks again for the great support!  I love Blesta and I am disappointed that I am forced to migrate away to a less user friendly platform...

[Unecrypted password API call]

Unfortunately I tried very hard to keep Blesta in our system.  Unfortunately I don't have a say.  Furthermore we continue to pay for licensing so why am I not untitled to support?

[Unecrypted password API call]

On 6/29/2017 at 2:56 PM, Tyson said:

Send everyone an email saying system changes necessitate they reset their password, then provide them a link to reset it.

That's what we're going to do.

Another question...where in the API can I get a list of credits that a client may have on their account?

[Unecrypted password API call]

Just now, Tyson said:

Why are you trying to get plain-text user passwords? You are aware of the security implications of this, correct? No one should ever know what someone's password is except for that person.

User login passwords cannot be decrypted because they were never encrypted to begin with. They are hashed, and that hash only works one way, so you will not be able to retrieve the plain-text version of the password from it.

It would be helpful to know what you're trying to accomplish here as there may be a better design you can employ to achieve it.

We're trying to migrate to a different system and we were trying to keep user logins the same...

[Unecrypted password API call]

I've written API code to access user login info BUT I'm dire need of using the system hash to decrypt the user password to plaintext.  Is there an API call that can be used to pass in the encrypted client password and our system has and return plaintext?

I'm making my call like this...

$client_login_password = exec("php index.php api/encryption/systemDecrypt.json -u api_user -k XXXXXXXXXXXXXXXXXXXXXXXXX -m GET -p \"value=" . $client_login_password . "\"");

[Custom Fields Not Showing Up For Existing Customers]

Workaround....

 

I modified the admin_clients.php file and made the following change to display custom fields for client group ID 1:

//$custom_fields = $this->Clients->getCustomFields($this->company_id, $client->client_group_id);
$custom_fields = $this->Clients->getCustomFields($this->company_id, 1);

[Custom Fields Not Showing Up For Existing Customers]

OK...I found my problem.  When I created the custom fields I only selected the client group general.  Is there not a way to allow all groups to share the same custom field?  In other words, do I have to created a custom field for each group even though it will have the same name (i.e Install Address)?

[Custom Fields Not Showing Up For Existing Customers]

We added three custom fields and when editing an existing customer those fields do not show up to be edited.  Am I missing somehting?