{"action":"created","issue":{"url":"https://api.github.com/repos/zaproxy/zaproxy/issues/1853","labels_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/1853/labels{/name}","comments_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/1853/comments","events_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/1853/events","html_url":"https://github.com/zaproxy/zaproxy/issues/1853","id":103425771,"number":1853,"title":"Technologies are not set from Context when scanning via REST API","user":{"login":"dap","id":42354,"avatar_url":"https://avatars.githubusercontent.com/u/42354?v=3","gravatar_id":"","url":"https://api.github.com/users/dap","html_url":"https://github.com/dap","followers_url":"https://api.github.com/users/dap/followers","following_url":"https://api.github.com/users/dap/following{/other_user}","gists_url":"https://api.github.com/users/dap/gists{/gist_id}","starred_url":"https://api.github.com/users/dap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dap/subscriptions","organizations_url":"https://api.github.com/users/dap/orgs","repos_url":"https://api.github.com/users/dap/repos","events_url":"https://api.github.com/users/dap/events{/privacy}","received_events_url":"https://api.github.com/users/dap/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-08-27T04:34:36Z","updated_at":"2015-09-10T17:54:45Z","closed_at":null,"body":"There appears to be no way to specify a list of technologies when invoking an active scan via the REST API. I think it would be beneficial if there was greater parity with the graphical UI in this respect, to allow for more specific scan targeting."},"comment":{"url":"https://api.github.com/repos/zaproxy/zaproxy/issues/comments/139325954","html_url":"https://github.com/zaproxy/zaproxy/issues/1853#issuecomment-139325954","issue_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/1853","id":139325954,"user":{"login":"dap","id":42354,"avatar_url":"https://avatars.githubusercontent.com/u/42354?v=3","gravatar_id":"","url":"https://api.github.com/users/dap","html_url":"https://github.com/dap","followers_url":"https://api.github.com/users/dap/followers","following_url":"https://api.github.com/users/dap/following{/other_user}","gists_url":"https://api.github.com/users/dap/gists{/gist_id}","starred_url":"https://api.github.com/users/dap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dap/subscriptions","organizations_url":"https://api.github.com/users/dap/orgs","repos_url":"https://api.github.com/users/dap/repos","events_url":"https://api.github.com/users/dap/events{/privacy}","received_events_url":"https://api.github.com/users/dap/received_events","type":"User","site_admin":false},"created_at":"2015-09-10T17:54:45Z","updated_at":"2015-09-10T17:54:45Z","body":"The API already allows for the specification of a context -- multiple contexts, in fact -- via the combination of importContext and setContextInScope. Were the API to be modified in the way that you indicate, there would still need to be code changes to respect the context-selected technologies at scan time. This is the reason for the referenced patch merging TechSet's. A given target may appear in scope in multiple contexts.\r\n\r\nAnd I concur that it would be reasonable and intuitive to have the API function similarly to the active scan GUI. In such case, I think that the API should respect the technology selections in both the context and active scan configuration."}}