Open kunalyadavdfe opened 7 years ago
@kunalyadavdfe Currently Job ID is locked to an Application Key. Another consumer would need to know both the Job ID and the associated Application Key.
If you want to increase the lock between Consumer and a Job the Job Provider can be extended to use a concatenation of SolutionId,ApplicationKey,Instance and UserId (if present) and the reference key.
This concatenation has been addressed in SIF Infrastructure Specification 3.2.1 which the inclusion of fingerprint.
"Security": SIF Functional Services Security - if one consumer gets hold of the job ID of another it can use that without any issues Currently there is no link between Environment registered to a consumer and the jobs created by a consumer. Potentially if the job ID is known then any consumer can use that job ID irrespective of whether they created the job in the first place or not