New passwords, entered into Phire, not matching with actual DB and PS passwords

We have a requirement to update our PeopleSoft system passwords, including the Peoplesoft connect ID.  after updating the connect ID password and validating Peoplesoft was working properly I went back to update the Phire configuration to use the same password.  After saving and the going back to test I found that the encrypted password from Phire does not match what Peoplesoft says it should.

I ran another test by reentering the exact same PeopleSoft password, no actual change just reentered, and see that the encrypted password does not match what it was previously.

How can I get Phire to encrypt the passwords the same way PeopleSoft is encrypting them so that Phire works.

this is critical since I can no longer migrate projects through Phire since the passwords are not being accepted.

1 Comment »

  1. Admin said,

    October 20, 2016 @ 12:48 pm

    Phire uses its own encryption mechanism, so the encrypted value will not directly match the value in the PeopleSoft tables.

    If this is still an issue to be resolved, then please contact Support at support@phire-soft.com for a closer look at your issue.

RSS feed for comments on this post

Leave a Comment

You must be logged in to post a comment.