4 of 4 people found this helpful
* reasoning/ranges/write - start a scan
* model/datastore/partition/DDD/read - to look at the current scan status
Depending upon other you code you may need permissions to start scans, look at the inferred model...
2 of 2 people found this helpful
And isn't "api/access" also needed in order to be able to use the REST API?
1 of 1 people found this helpful
Given the post I was assuming talking about IP specific things not what you need to access the REST API in the first place.
Thanks for the answers - will test and respond back!
3 of 3 people found this helpful
Plus if you were using a token rather than authentication you would not just want api/access as otherwise your account would be deactivated after a period of time - you would also want security/user/never_deactivate.
In this case the account is an Active Dir windows account. It will have group membership to a security group in AD as well. That security group will be mapped in the Discovery LDAP Group mapping to the new group I build with the minimal perms.