SendGrid with Jiwa

[Mike.Sheen]

Nope. Reset the SMTP password plenty of times thinking that it was wrong.

In that case, messagebox out encryptionObject.ErrorMessage and it might provide the reason for the exception.

If it's "Invalid encryption type specified" then it's an environment issue - it doesn't have the required cryptographic cipher suites available, and you're likely ALSO silently getting this error when resetting the password (SELECT * FROM HR_Staff would reveal this - look for any rows with "ERROR" as the SMTP Password).

It it's "Both a string and a key are required" then the password contains unacceptable characters, or there is something funky going on with the environment culture and datetime formats.

[SBarnes]

Hi Danny,

Below is a section of code from one of our customers web stores into which the staff can login to, it uses the normal password and compares the encrypted values but largely the code could be changed to have a look at what's going on for the smtp one as well you just need to change it to use the smtp encrypted value and smtp last saved date and change request.LogonPassword to what ever value you are wanting to check.

Code: Select all

JiwaFinancials.Jiwa.JiwaServiceModel.Tables.HR_Staff hrstaff = Db.Select<JiwaFinancials.Jiwa.JiwaServiceModel.Tables.HR_Staff>().Where(s=> s.SName.ToUpper() == request.LogonCode.ToUpper() ).FirstOrDefault();
            if (hrstaff == null)
            {
               return result;
            }
            JiwaFinancials.Jiwa.JiwaEncryption.JiwaEncrypt jiwaEncrypt = new JiwaFinancials.Jiwa.JiwaEncryption.JiwaEncrypt();
            DateTime PDate = hrstaff.PasswordLastChangedDateTime == null ? DateTime.Now : (DateTime) hrstaff.PasswordLastChangedDateTime;
            string pwdenc = jiwaEncrypt.EncryptString(request.LogonPassword, manager.Database.FormatDateTime(PDate, true));


to get an ORM Lite database connection, Db in the above code, you do something like this

Code: Select all

  var dbFactory = new OrmLiteConnectionFactory(manager.Database.ConnectionString, ServiceStack.OrmLite.SqlServer2012Dialect.Provider);
var db = dbFactory.Open()


[DannyC]

messagebox out encryptionObject.ErrorMessage and it might provide the reason for the exception

"Not a valid hex string"

And to add a bit more info...Using Stuart's code above I have also confirmed that the encrypted HR_Staff.SMTPPassword is identical so I'm comfortable that the p/w has been encrypted and saved correctly.

[Mike.Sheen]

messagebox out encryptionObject.ErrorMessage and it might provide the reason for the exception

"Not a valid hex string"

And to add a bit more info...Using Stuart's code above I have also confirmed that the encrypted HR_Staff.SMTPPassword is identical so I'm comfortable that the p/w has been encrypted and saved correctly.

I can tell you the code in the plugin to obtain the SMTP Password and decrypt it is identical to the code in the staff maintenance form business logic - so I believe it has got to be an environment thing.

[Mike.Sheen]

Provide us with the SMTP Password text stored in the database, and the SMTP Last saved date time value in HR_Staff.

[DannyC]

Will send via email

[Mike.Sheen]

Will send via email

No, don't do that.

If you can change the password via the Staff maintenance form as you said you can, just change it to "password" first and then send that.

It's not sensitive that way.

[DannyC]

Bugger, too late! The SMTP password is defined by my client's IT people & I don't have access to change it. Any way you've got the real p/w now.
I can fairly easily get their IT people to alter it later but for now let's just work with what we've got.
I'd rather that as it might be some decryption issue with special characters, not just 0-9 or A-Z.

[Mike.Sheen]

Updated plugin attached.

Problem was that the plugin was decrypting the SMTP password when it was already decrypted.

[DannyC]

Bingo!

Deployed and tested. All good.