Password reset by user

[Former Member]

Dears,

I have recently installed BI 7.0 IDES server.Now I want that on Java Stack of server users should be able to reset their passwords themselves.

For it I have set the parameter

ume.logon.logon_help to true

And maintained our SMTP server IP in portal UME configuration.

But Now issue when I trying to reset by password by "Get Support" option.

and entering my last name,first name and login ID.

Its showing incorrect user information.

While i checked several times I am providing right information.

So please suggest is there any other mandotory step also to configure it.

I used link : http://help.sap.com/saphelp_nw70/helpdata/EN/43/3d77734ae830f3e10000000a11466f/frameset.htm

Please Suggest.

Deepak

Edited by: Deepak Mittal on May 6, 2009 9:48 AM

[Former Member]

Hi Deepak,

when you say it shows the wrong information, what shows the wrong information and how is the information wrong?

Dion

[Former Member]

Dears,

As you know when we click on password reset in Get Support option.It asks for Last Name,first Name and emai ID.

After enter these information when I click on Submit,It shows:

Incorrect user information, cannot send e-Mail with new password

While user information is same as mentioned in user master records.

So I am thinking,I am missing something in process.

Please Suggest.

Deepak

[Former Member]

You need to make sure you have UME setup to send emails and your users need to have a valid email address...

[Former Member]

Dear Deepak,

If your SP level is >12 then follow the below steps:

Set ume.logon.logon_help in Visual Admin to False

Create a role and assign Logon_Help UME action to that role.

Assign the role to 'Anonymous' group.

This will open a webdynpro application for password reset.

If it still doesnt work

Then Uncheck "Require First and Last Names in Logon Help" option from UME configuration in System Admin - > UME Configuration - > User Admin UI

Hope this helps.

Regards,

Nirmal Sivakumar G

[Former Member]

That sounds like a data issue on the SU01 record. Make sure all the details on the SU01 record exist and are accurate.

cheers,

Dion