You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// <param name="asUser">The user ID to set as the 'As-User' header parameter; used to make calls in the context of a user using an admin token</param>
56
+
/// <param name="suppressNotifications">Whether or not to suppress both email and webhook notifications. Typically used for administrative API calls. Your application must have “Manage an Enterprise” scope, and the user making the API calls is a co-admin with the correct "Edit settings for your company" permission.</param>
57
+
/// <returns>BoxClient that uses CCG authentication</returns>
that represents it and can perform API calls. The Service Account is separate
55
55
from the Box accounts of the application developer and the enterprise admin of
56
56
any enterprise that has authorized the app — files stored in that account are
@@ -85,8 +85,7 @@ adminClient.Auth.SessionAuthenticated += delegate(object o, SessionAuthenticated
85
85
};
86
86
```
87
87
88
-
App auth applications also often have associated App Users, which are
89
-
[created and managed directly by the application](https://developer.box.com/en/guides/authentication/user-types/)
88
+
App auth applications also often have associated [App Users](https://developer.box.com/guides/getting-started/user-types/app-users/), which are created and managed directly by the application
90
89
— they do not have normal login credentials, and can only be accessed through
91
90
the Box API by the application that created them. You may authenticate as the
92
91
Service Account to provision and manage users, or as an individual app user to
@@ -115,7 +114,7 @@ Server auth allows your application to authenticate itself with the Box API
115
114
for a given enterprise.
116
115
Client Credentials Grant (CCG) allows you to authenticate by providing `clientId` and `clientSecret` and `enterpriseId` of your app.
@@ -139,8 +142,12 @@ adminClient.Auth.SessionAuthenticated += delegate(object o, SessionAuthenticated
139
142
};
140
143
```
141
144
142
-
App auth applications also often have associated App Users, which are
143
-
[created and managed directly by the application](https://developer.box.com/en/guides/authentication/user-types/)
145
+
Second way leaves token management (caching) to the `Auth`, a new token is retrieved before the first call. Keep in mind that if you create multiple `adminClient` instances, the token won't be shared, it is expected that the `adminClient` instance is reused.
146
+
```c#
147
+
IBoxClientadminClient=boxCCG.AdminClient();
148
+
```
149
+
150
+
App auth applications also often have associated [App Users](https://developer.box.com/guides/getting-started/user-types/app-users/), which are created and managed directly by the application
144
151
— they do not have normal login credentials, and can only be accessed through
145
152
the Box API by the application that created them. You may authenticate as the
146
153
Service Account to provision and manage users, or as an individual app user to
@@ -155,6 +162,10 @@ instance as in the above examples, similarly to creating a Service Account clien
0 commit comments