Skip to Content
0
Former Member
Sep 14, 2005 at 07:01 PM

When to use ConvertPasswordToUpperCase flag?

24 Views

Howdy,

Our software product uses SAP .NET connector to exchange data with SAP. The end user needs to specify logon fields such as hostname, username, password, system number, etc. The user saves this information, along with some other information, as documents.

We just moved our code to use version 2.0.1 from 2.0 of .NET connector and things stopped working :-(. We got into invalid username/password error, an issue that has already been discussed on this forum. It turns out version 2.0 was not case sensitive about the passwords and the new version is.

This change will break all the documents for our existing customers when they upgrade our product.

Q1. When a document is loaded, we know the version number the document was created with. As part of automatic conversion, my thought is that we must simply convert existing passwords to uppercase. Will this work?

Q2. When the user tries to create a new connection, we display our UI for hostname, username, password, etc. Logically, it doesn't make sense for us to ask a new queston - "Do you wish to convert the password to uppercase?" They might as well type the password in uppercase. What do you think the right behavior should be?

Q3. Under what circumstances one must use Destination.ConvertPasswordToUppercase flag?

Thank you in advance for your help.

Pradeep