Support link in Portal logon page not working

Question

Hi All,
We are using the ´support´ link on the logon page of our Portal. When we click the support link, the system asks for UserId and e-mail adress. When we fill this in correctly, the system responds by displaying "New password sent to e-mail adress".
However, the password is not reset or anything and we still have to logon with the original old password. Where can this problem be rooted and where do I start to look for the cause of this.
We are using CUA and this is set on ECC 6.0 production system.
Message was edited by:
        Jan Laros

Answer 1

Hai Laros,
I have gone through this issue...
I think your Portal is EP 7.0 SP12..
For logon page weare using two jar files umelogonbase.jar and com.sap.portal.runtime.logon_api.jar
There is some change in code of umelogonbase.jar file  in SP12  
com.sap.security.core.sapmimp.logon.logonbean method getLogonHelp
In SP12
   public boolean getLogonHelp()
        boolean rc = mySAPProperties.getBoolean("ume.logon.logon_help", true);
        if(!rc)
            rc = checkPermission("LOGON_HELP");
        return rc;
private static boolean checkPermission(String permissionName)
        String METHOD = "checkPermission";
        boolean hasPermission = false;
        if(trace.bePath())
            trace.entering("checkPermission", new Object[] {
                permissionName
        try
            boolean flag1;
            try
                IUser user = UMFactory.getAuthenticator().getLoggedInUser();
                if(user == null)
                    user = AnonymousUser.getInstance().getAnonymousUser();
                if(trace.beDebug())
                    String userName = user != null ? user.getName() : "no user";
                    trace.debugT("checkPermission", "The current user is [{0}].", new Object[] );
                if(user != null)
                    LogonApplicationPermission permission = new LogonApplicationPermission(permissionName);
                    hasPermission = user.hasPermission(permission);
                } else
                    trace.errorT("checkPermission", "The current user is null.");
                boolean flag = hasPermission;
                return flag;
            catch(UMException umex)
                flag1 = false;
            return flag1;
        finally
            if(trace.bePath())
                trace.exiting("checkPermission", new Boolean(hasPermission));
In SP10 code was
  public boolean getLogonHelp()
        return mySAPProperties.getBoolean("ume.logon.logon_help", true);
In your jsp page
if ( logonBean.getLogonHelp() ){
//code
logonBean.getLogonHelp() retuning true because of  additional <b>LogonApplicationPermission</b> checking....  
I think you got my point....
With reagrds
Eldose
Eldose