Archive for Security

Encryption on the Code during Transit

Does PHIRE encrypt the code in transit between the environments?

Comments (1)

Phire version installed

As I know what version of Phire I have installed with a unix script or database. The query is if there is any script to be able to ask that As I know what version of Phire I have installed with a unix script or database. The query is if there is any script to be able to ask that question

Comments (1)

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.

Comments (1)

Use of the “Allow Object Edits” and “Allow Script Edits” options

What are the these options used for?  Do they prevent users from making object or script changes?

Comments (1)

Security adding scripts

How do I restrict adding scripts to a Developer role ?
ie: I only want developers to be able to Add Scripts to a CR, once a CR has been migrated beyond the Development DB I want to stop scripts being added.

Comments (1)

How to setup so nobody can create a new CR using a particular CR Type?

First, leave the CR Type “active”, so that it continues to be visible in the searches.  Then go to the Row Level Security component (Phire Architect > Security Administration > Row Level Security) and remove the permission to “Create New CR” for that CR Type.  You’ll need to do that for each role that might have access to create a new CR.  In the end, the users will be able to search for and open the existing CRs with that type, but nobody will be able to create a new one.

Comments

How to enable developers to download files from different environments?

Developers can access files (SQRs, COBOLs, etc.) that are residing on the servers for the various environments from the Objects page within the Change Request. First, the developer needs to add the file name to the CR Object list. Then to download or upload the file from/to an environment, the developer needs to click the download or upload button next to the file name in the CR Objects. The prompt page will offer a list of databases available to the developer.

The list is controlled by setup in the Domain Setup Wizard on Step 14. Workflow Databases (found at Phire Architect > Architect Administration > Domain Setup Wizard).  There you will find the “File Upload” and “Object View/Download” options listed for each database within each CR Type.  The file upload option is further limited by “Restore Object” security and the lock status of the particular file within Phire.

Comments

How to disable the auto-assign checkbox on the Issue without customizing?

You can disable the auto-assign checkbox on the issue component without customizing. This is done through Phire security. Navigate to:  Phire Architect > Security Administration > Domain Security

Select the Role from which you want to take away the auto-assign checkbox.
Click the Permission List link next to your Domain.
Uncheck the “Override Auto Assignment” permission.

Note: If the user belongs to multiple roles, you need to make you take away the above permission from all the roles. If at least one role assigned to a user has this permission, then the auto-assign checkbox will still be enabled.

Comments

How to create a read-only user account for CRs?

We deliver a role that is designed to provide a read-only view for users, which is named PHI_CR_READONLY_ROLE.  Remember to setup Domain Security for the role within Phire so it can access the domain and search for Change Requests.  The only permission the role needs is “Open Existing CR” to open CRs in that domain and look around.

Comments

How can we make the assignment field on future tasks entry capable?

If the assignment field on future tasks in the workflow are made display only, then this indicates that the current user does not have permission to reassign tasks.  That permission is granted here:  Phire Architect > Security Administration > Reassign Task Security.  The permission is granted to either a role or an individual user, similar to the other permission sin Phire.  And it can be granted to all task types, or specific task types depending on the requirements being met.

Comments