In this use case, deployments from the main branch are configured to resolve against a user account derived from the GitHub repository_owner claim. This allows the “Deployed By” field in Artifactory to display a meaningful user (rather than a generic service account or provider reference) while still applying controlled permissions.
An identity mapping named all-main-branch-commits was created with the following parameters:
{
"name": "all-main-branch-commits",
"provider_name": "jeremyl-frog",
"claims": {
"ref": "refs/heads/main"
},
"token_spec": {
"scope": "applied-permissions/user",
"username_pattern": "{{repository_owner}}"
},
"priority": 1
}
On the Artifactory side, a user account matching the repository owner (jeremyl-frog) was created and added to the jl-github-ci permission group. After running the workflow, deployments from the main branch now appear as Deployed By: jeremyl-frog in Artifactory.
Artifact properties added in the workflow (such as committer and GitHub actor) remain intact, so traceability to the individual who triggered the workflow is always preserved.
