|
||||||||
|
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/groups/opt_out.
Can you please clarify on this:
C:\gnuwin32\bin> .\wget.exe --auth-no-challenge --http-user=user --http-password=_apiToken_ http://myserver.com:8080/job/Experiment-Main-Build/build?token=1715b88bfba6717fadee72f5d5ecd17a
The word "apiToken", is that ment as a keyword so that the final "?token=1715b88bfba6717fadee72f5d5ecd17a" is interpreted correctly or is that a placeholder for the users api token??
@Jeff imho no AD/LDAP request is needed at all. Jenkins should bypass what ever auth scheme it has as long as the user and his apikey is correct.