|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I think I understand both cases described here. It sounds similar but not identical something related I see. I thought I'd check before logging a separate defect.
LDAP authentication is enabled on my master.
I have an api token associated with my user. (I have admin privileges).
I'm attempting to retrieve the config.xml for a particular computer using basic authentication in groovy.
For instance:
http://myjenkins/computer/a-slave-node-computername/config.xml?token=TOKEN
I'm passing in my username and my token for the password field.
I get a 403 error.
I think what your saying is that I should be expecting a 403 unless the code was enhanced to allow a GET on the computer config using a token.
I'm at build 1.505
Is this a separate issue or an RFE? I realize the error described above is not a 403 but another exception. I still wasn't sure if that was because the GET was attempted for the master...and in my case it's a request for slave node configuration.
Thanks!