Updgrade Issues with case sensitive passswords in EEC6

[charmaine_greene]

Hi

We have just upgraded from 4.6c to ECC6 and are experience issues with users unable to logon with the old production password (password used in 46c).

I am aware that this functionality is now SAP standard however In EEC6 we are not forcing users to use case sensitive passwords. Its their choice if they want to set the password with case sensitive

The following parameters are set to 0

login/min_password_uppercase

login/min_password_lowercase

We find that some users have not been able to use their orginal password in the new upgraded EEC6 production enviroment and not sure of the reason why. I have searched OSS for any issues but cannot find note that describes this issue.

Has anyone else expereinced similar problems after an upgrade.

Regards

Charmaine

[charmaine_greene]

Hi

We have just upgraded from 4.6c to ECC6 and are experience issues with users unable to logon with the old production password (password used in 46c).

I am aware that this functionality is now SAP standard however In EEC6 we are not forcing users to use case sensitive passwords. Its their choice if they want to set the password with case sensitive

The following parameters are set to 0

login/min_password_uppercase

login/min_password_lowercase

We find that some users have not been able to use their orginal password in the new upgraded EEC6 production enviroment and not sure of the reason why. I have searched OSS for any issues but cannot find note that describes this issue.

Has anyone else expereinced similar problems after an upgrade.

Regards

Charmaine

[Former Member]

Hi Charminee,

I am doing the upgrade too ..but on two -- boxes - both sand boxes did not encouter this at all !! But Iam surprised -- does all the users have this problem ??

[Former Member]

try to set profile parameter login/password_downwards_compatibility=5, this parameter can be changed dynamically.

cheers,

-Sunil

[Former Member]

Sunil,

I have done your suggestions and that looks good !! ie : min for lower /upper case : 0 and down ward compatiplity 5

Did you change them on instance profile or default ??

Thanks

[charmaine_greene]

Hi

I was looking at this a few days ago and decided to set this in our QA system.

The value was initally set to 0 and I have set this to 3. From what I understand the passwords are stored differently in hash tables between the 2 systems and this parameter is used to do the conversion when users log on to the new system for the first time. Problem is that I do not know the right setting. The plan is to test this setting by getting some users who have not logged yet. Unfortunately my project manager is nervous about putting this into production and would rather take the pain of resetting user passwords when requested.

Also think Julius is right about this also being a training issue as some users may have simply forgot their passwords.

I would like to fully understand the settings for this parameter so that I know what to use for future upgrade projects. If someone could point me to some material (in plain english) it would be a great help.

Many thanks.

Charmaine

[charmaine_greene]

ry to set profile parameter login/password_downwards_compatibility=5, this parameter can be changed dynamically.

cheers,

-Sunil

Hi Sunil

Ok, this sounds better than the value = 3, I will try this and see. If its a dynamic setting it makes sense to use this.

Regards

Charmaine

[Former Member]

Chaminee: before you set it to zero what was the value earlier ?? This answer would help me to set mine too.

Thanks

[charmaine_greene]

Chaminee: before you set it to zero what was the value earlier ?? This answer would help me to set mine too.

Hi,

I think this value is default for SAP - as we do not want to force users to use lower/uppers case values in their passwords this value will be left at = 0.

Charmaine

[Former Member]

Perhaps it is just a training issue...

> We have just upgraded from 4.6c to ECC6 and are experience issues with users unable to logon with the old production password (password used in 46c).

Users in older releases sometimes did not notice that their passwords were converted to uppercase, and might enter the first or other characters with "Shift +" and not thought about it. It could even be a keyboard problem.

Although they can still use the old password and are not forced to use both cases (as per your params), the password is still case-sensitive, so little "typos" (typing errors) like "teh" and "SAp" or hitting the "CAPS LOCK" key to expect the same result is causing this.

This might also explain THE WHOLE MESSAGE POSTED IN CAPS LOCK which we see sometimes here at SDN?

If you do not force, but rather train the user to use a more personalized password or "pass phrase" then this might solve the problem, even if they are still expecting the 8 character, converted to uppercase, result...

Cheers,

Julius