Regenerated library to pick up latest schema changes

Author: petemoore

codegenerator/model/model-data.txt

@@ -20,9 +20,6 @@ calling TaskCluster APIs.
 
 The client's scopes control the client's access to TaskCluster resources.
 The scopes are *expanded* by substituting roles, as defined below.
-Every client has an implicit scope named `assume:client-id:<clientId>`,
-allowing additional access to be granted to the client without directly
-editing the client's scopes.
 
 ### Roles
 A _role_ consists of a `roleId`, a set of scopes and a description.
@@ -36,13 +33,6 @@ located at the end of a `roleId`. If you have a role with the following
 `roleId`: `my-prefix*`, then any client which has a scope staring with
 `assume:my-prefix` will be allowed to assume the role.
 
-As previously mentioned each client gets the scope:
-`assume:client-id:<clientId>`, it trivially follows that you can create a
-role with the `roleId`: `client-id:<clientId>` to assign additional
-scopes to a client. You can also create a role `client-id:user-*`
-if you wish to assign a set of scopes to all clients whose `clientId`
-starts with `user-`.
-
 ### Guarded Services
 The authentication service also has API end-points for delegating access
 to some guarded service such as AWS S3, or Azure Table Storage.

src/main/java/org/mozilla/taskcluster/client/auth/Auth.java

@@ -26,9 +26,6 @@
  * 
  * The client's scopes control the client's access to TaskCluster resources.
  * The scopes are *expanded* by substituting roles, as defined below.
- * Every client has an implicit scope named `assume:client-id:<clientId>`,
- * allowing additional access to be granted to the client without directly
- * editing the client's scopes.
  * 
  * ### Roles
  * A _role_ consists of a `roleId`, a set of scopes and a description.
@@ -42,13 +39,6 @@
  * `roleId`: `my-prefix*`, then any client which has a scope staring with
  * `assume:my-prefix` will be allowed to assume the role.
  * 
- * As previously mentioned each client gets the scope:
- * `assume:client-id:<clientId>`, it trivially follows that you can create a
- * role with the `roleId`: `client-id:<clientId>` to assign additional
- * scopes to a client. You can also create a role `client-id:user-*`
- * if you wish to assign a set of scopes to all clients whose `clientId`
- * starts with `user-`.
- * 
  * ### Guarded Services
  * The authentication service also has API end-points for delegating access
  * to some guarded service such as AWS S3, or Azure Table Storage.