that is correct. I turned off complex password rules (pretty much all of the rules) and made the password textbox show clear text, just to make sure it wasn't a typo.

Did you see my last post about packaging up your SQL database and project so I can take a look at it?

How much of it do you need? I'm converting a proprietary app, most of which isn't for public consumption. There are two dbs, the StrataFrame db and the app db. The app db has something like 90 tables, a 100 views and 150 sprocs. Some of the tables have lots of data (even in my test db)...yada yada. I can't send most of it to you, as I'd be skinned alive by my boss. So, I can't really just zip it up and post it here



So, what exactly do you need?

Well...I thought you might be working with a test app since you are going through the trial.  Bottom line is I need to reproduce the behavior.  Let me try it on my side first.

Well, the app we need to use it on is complex. Rather than invent the complexity, I'm trying the "hard" stuff with SF to evaluate it. Plus, I needed to see how it would handle existing data and I have data in the db to test on and I have databases that I can connect to over VPN to test speed, etc.



However, I'm going to do a new app, and see if I can reproduce, and on a test app, so I can send it to you if it is reproduced.

ahhhh....it just dawned on me what you forgot to set.  You do not have the security key and vector set to match your project.  If you look in the documentation under: Defining Security within the Application -> Adding Security to an Existing Application then go to section 5b to see how to call this method.

It has to match the security key defined in your Role-Based Security project.  Since all of the password, etc. are encrypted, this is your "pre-shared" key to dynamically create a vector encryption key.  Here is the screen inside of the editor:

Whatever value you have in the Security Key property here you need to have that also defined within your app (case sensitive) in the InitApplication section:

SecurityBasics.SetSecurityKeyAndVectorForUserAuthentication("Test")

As you suspected, this was not set.



I made both the same, but it still didn't work.



I'm gonna guess that this is because the security key set in the security dialog is used to encrypt the values stored in the db, while the on set in InitApplication is used to decrypt this value right? So, I need to set it to the string in the security editor, which was an empty string...trying it...

Yes...set this in the role-based security editor, then set the password for the user...then make sure it matches in the InitApplication and I think you will be good.  I just created a test app doing what you are attempting to do and it worked fine....so we just need to work through this little step and you should be on your way.

Wohoo! That was it. When set to the value in the security dialog, all is good. I'll make sure I keep these both set in the future. Thanks Trent!

Good!   I will keep this in mind the next time I see these results happening in the field...I bet you won't soon forget this step either