Standard Error Messages in Custom Change Password Screen

Question

Hi All,
I've developed a custom change password screen in Web Dynpro. I want to use the standard messages that appear in the portal logon screen. I looked in the portal logon par and got the umelogonbase.jar and found in my eclipse dir the com.sap.security.core.jar wich this last one depends. I put then in an externallib and wrapped them in a JEE lib. Declared dependency from my WD DC to the JEE lib and added the library reference in the WD DC.
I have the following code:
try {
     IUserAccount userAcc = UMFactory.getUserAccountFactory().getUserAccountByLogonId(wdContext.currentInfoElement().getLogon());
     userAcc.setPassword(wdContext.currentInfoElement().getOldPassword(), wdContext.currentInfoElement().getNewPassword());
} catch (UMException e) {
     e.printStackTrace();
     error = true;
     LogonMessageBean bean = new LogonMessageBean(WDClientUser.getLoggedInClientUser().getLocale());
     String msg = bean.print(new Message(e.getMessage()));
     wdComponentAPI.getMessageManager().reportWarning(msg);
But when I try to execute my app I get the following exception:
   java.lang.VerifyError: (class: com/cafedecolombia/ols/um/ChangePassword, method: test signature: ()V) Incompatible object argument for function call
    at com.cafedecolombia.ols.um.wdp.InternalChangePassword.(InternalChangePassword.java:109)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    ... 28 more
Does anyone has successfully done this? Is there any other dependencies? Is there an EASIER way to do this? Is there any initialization needed?
Any help will be highly appreciated.
Regards,
Andrés Acero

Answer 1

Ok so here is how I solved it.
I found this very interesting article called "SAP Authentication Guideline" and there the author mentions that the messages are defined in class SecuritPolicy of the core security jar. So with that in mind this is how my code finally worked out:
try {
     IUserAccount userAcc = UMFactory.getUserAccountFactory().getUserAccountByLogonId(wdContext.currentInfoElement().getLogon());
     IUserAccount mutableUserAcc = UMFactory.getUserAccountFactory().getMutableUserAccount(userAcc.getUniqueID());
     mutableUserAcc.setPassword(wdContext.currentInfoElement().getOldPassword(), wdContext.currentInfoElement().getNewPassword());
     mutableUserAcc.commit();
} catch (UMException e) {
     e.printStackTrace();
     error = true;
     ISecurityPolicy policy = SecurityPolicyFactory.getInstance().getSecurityPolicy();
     wdComponentAPI.getMessageManager().reportWarning(policy.getLocalizedMessage(WDClientUser.getLoggedInClientUser().getLocale(), e));
Here is a link to the article on SDN:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/599ab890-0201-0010-12a1-b988e3a09735
If you have any comments please do.
Cheers,