Forum

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.

How to configure project naming convention so we can migrate the same project definition name from source to target environments including the project definition properties and comments? For example – When developers create a PeopleSoft project and they need to update the Project definition properties (who, when, incident number, what changes or why its need etc). We need to migrate same project definition (including properties) to other environments.