We have a customer client that our users use to change their password. In our code we just validate that the password inputted is not null and not spaces. Then we call the setPassword in the Request Context getExecutionService().setPassword() method. I have followed the code all the way back to the FMCService and FmcSyntaxChecker.
The issue is when I test changing the password in our development and test environments with the password having either the @ and/or # in it, it fails because these symbols are not java identifiers. This is how is should work. But when I change the password in our production environment, it doesn't work. It allows the users to have either the @ and/or # in their password.
I have researched everything I can think of from looking at the code in all jar files, looking at the server configurations, etc. and have not figured out why it is working this way.
The only thing I can think of doing next is some how turning on tracing so I can see if the code in FmcSyntaxChecker is being utilized in all environments.
How do I turn tracing on so I can see if the code is being processed?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2009-07-25T14:20:57Z by jmac_EmeriCon
Pinned topic Change password using com.ibm.workflow.client.api.FMCService
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-07-25T14:20:57Z at 2009-07-25T14:20:57Z by jmac_EmeriCon
jmac_EmeriCon 110000S3HB26 PostsACCEPTED ANSWER
Re: Change password using com.ibm.workflow.client.api.FMCService2009-07-25T14:20:57Z in response to SystemAdminNot sure how this might apply, but @ and # are treated specially on mainframes along with $ they are considered alpha characters. Are we talking about different platforms in what you are testing?