Using setmembers with environment api keys

Archive Rancher 1.x
1

Hi,

I am trying to use the API and specifically the setmembers action on a project.

curl -v -d '{"externalId":"CN=Jos Houtman,OU=KvK,OU=Gebruikers,DC=win,DC=k94,DC=kvk,DC=nl", "externalIdType":"ldap_user", "role":"owner"}'  "http://XXXX:AAAA@rancher.sbx.k94.kvk.nl/v2-beta/projects/1a1563014/?action=setmembers"

This works when using personal API keys, but not when using environment API keys.
The documentation states: The key is owned by the Environment and has full access to manage that Environment, but no access to any others (http://rancher.com/docs/rancher/v1.6/en/api/v2-beta/)

So my question, is this a bug in the code or in the documentation?

{"id":"1a50f100-cfae-49db-8446-e36fd4f5c00b","type":"error","links":{},"actions":{},"status":422,"code":"ActionNotAvailable","message":null,"detail":null,"fieldName":"action","baseType":"error"}
2

Environment keys can manage everything in the environment, but not the environment (and its members) itself.

If this were allowed, there would effectively be no difference between owner and member because members can make API keys.