# 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/Problem].  Required.
#                 Feature and Bug are common terms.
#                 A Problem is suspected bug, or one without a clear
#                 understanding of exactly what is broken.
#
#  Release:       Release in which job is intended to be fixed.

Job:	SDP-793

Status:	open

Project:	perforce-software-sdp

Severity:	C

ReportedBy:	clouie

ReportedDate:	2022/05/16 20:04:52

ModifiedBy:	tom_tyler

ModifiedDate:	2022/05/16 20:04:52

OwnedBy:	tom_tyler

Description:
	Remove refs to service user password.
	
	The SDP references a service user password in several places
	in both Linux and Windows SDP.  This is not needed as we
	advise setting crazy/big generated password for service users,
	and then not capturing it anywhere.
	
	The way to login a service user is by logging in first as a
	regular super user, and then as the regular super, generating
	a ticket for the service user. On Linux, this can be done with
	
	p4login -v service
	
	Docs should be reviewed to ensure there is no conflicting info.
	
	This change will need minor doc changes in Windows and Linux,
	as well as setup scripts for each platform to clarify how the
	password is generated for service users.  Note that the
	mkrep.sh script already sets and discards long service user
	passwords, which is the desired behavior.

Component:	setup

Type:	Feature