Context

Currently we have defined the Authorize Project to use the following order to identify the user to run a job as:

1. Configuration defined at the level of the job
2. Run as "any developer" (limited role basically)

I wanted to introduce an intermediary step "Run as owner".

The issue here is that the ownership plugin doesn't check if ownership is defined and returns "Anonymous" if one of the following conditions is true

1. Ownership is disabled
2. There is no primary owner defined

While I'm not too sure about the latter, I'm pretty sure that the former is causing us an issue: on most of projects owners are not defined... And thus our jobs get to run as "Anonymous" ... Which obviously means it doesn't run !

Acceptance criteria

• If ownership is disabled the "Run as owner" should basically be identified as "nothing defined" and Authorize project should proceed to the next policy.