| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Change password using com.ibm.workflow.client.api.FMCService |
« View previous topic :: View next topic » |
| Author |
Message
|
| KimberlyLewis |
 Posted: Thu Jul 16, 2009 9:33 am Post subject: Change password using com.ibm.workflow.client.api.FMCService |
 |
|
Newbie
Joined: 16 Jul 2009
Posts: 2
|
We have a custom 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? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Jul 16, 2009 9:43 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| 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. |
OK. It fails in test and development.
| Quote: |
| But when I change the password in our production environment, it doesn't work. |
And it fails in production, too.
| Quote: |
| It allows the users to have either the @ and/or # in their password. |
I'm confused. Does it work or not?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 16, 2009 9:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It fails to fail in production, Bruce. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jul 16, 2009 9:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| It allows the users to have either the @ and/or # in their password. |
Seems to me that this statement means that it did, in fact, work.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| KimberlyLewis |
| Posted: Thu Jul 16, 2009 10:15 am Post subject: |
|
|
Newbie
Joined: 16 Jul 2009
Posts: 2
|
The code in development and testing environments will not allow the user to have the @ or # in their password. That is the correct behavior. But in production it does allow the user to have @ or # in the production. This is the wrong behavior.
I would like to turn trace on so I can see if the code that validates the password is being hit in production. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
