I have a similar problem. we use

  • Jenkins LTS 1.580.1
  • project based matrix acls
  • authentication via ldap

reproduce:

  • create dummy job
  • project based access-control forbids anonymous users
  • add a user with read and build permissions
  • get an API token for that user
  • (I also have a build trigger token, but I don't know if that matters)
  • (optional: activate "Build User Vars" plugin and echo ${BUILD_USER} in a bash script)
  • trigger the job with curl --user me:apitoken https://server/job/test/build?token=ASDF
  • (I have a parameterized build, but again I don't know if that matters)

Expected Result:

  • build triggers
  • build info contains "Started by <user>"
  • (bash script shows <user> as $BUILD_USER)

Actual Result:

  • build triggers (i.e. authentication was granted)
  • build infos says "started from remote computer <IP>"
  • ($BUILD_USER not set in bash script)

To me, this sounds related to the original issue description. Although access via the API token is granted (and no exceptions are thrown), the user data itself is not known to core (build info) or plugins (build user vars).

I consider this functionality critical, because it gives us an easily readable protocol of users that have triggered a certain job (i.e. traceability).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to