# The form data below was edited by tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: HI-8 Status: punted Project: perforce_software-helix-installer Severity: C ReportedBy: tom_tyler ReportedDate: 2019/01/11 12:12:05 ModifiedBy: tom_tyler ModifiedDate: 2019/06/27 10:31:30 OwnedBy: tom_tyler Description: Added -saml flag to build SAML-enabled Helix Server. Adding the '-saml' flag will: * Download the Perforce SAML Python triggers. * Install the Python dependencies of the SAML triggers. * Install the Perforce SAML Python trigger and config files in and SDP-style location, /p4/common/bin/triggers/saml * Generate bogus trigger configuration files with 'EDTIME' tags indicating where customization is required, e.g. the URLs that must be plugged in for Okta, Ping Federate, OneLogin, etc. * Set the following conifgurables: p4 configure set auth.sso.allow.passwd=1 * Enable SAML trigger in the Perforce triggers table. * Set big/bogus passwords for all users, except for the 'perforce' admin super user that won't use SAML, and will authenticate using the standard demo password stored in /p4/common/config/.p4passwd.p4_1.admin. DevNotes: This has been punted due to planned deprecation of the first SAML implementation that this job was for. A new "Helix Identity Integration" solution coming out in late 2019 will be more transparent, requiring no special client side support for SAML support. Component: core Type: Feature