files.com 1.2.191 → 1.2.192
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -5
- package/_VERSION +1 -1
- package/lib/Files.js +1 -1
- package/package.json +1 -1
- package/src/Files.js +1 -1
package/README.md
CHANGED
|
@@ -63,12 +63,14 @@ To initiate a support conversation, you can send an [Authenticated Support Reque
|
|
|
63
63
|
|
|
64
64
|
## Authentication
|
|
65
65
|
|
|
66
|
+
There are two ways to authenticate: API Key authentication and Session-based authentication.
|
|
67
|
+
|
|
66
68
|
### Authenticate with an API Key
|
|
67
69
|
|
|
68
70
|
Authenticating with an API key is the recommended authentication method for most scenarios, and is
|
|
69
71
|
the method used in the examples on this site.
|
|
70
72
|
|
|
71
|
-
To use
|
|
73
|
+
To use an API Key, first generate an API key from the [web
|
|
72
74
|
interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
|
|
73
75
|
SDK](/javascript/resources/developers/api-keys).
|
|
74
76
|
|
|
@@ -90,14 +92,14 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
|
|
|
90
92
|
|
|
91
93
|
### Authenticate with a Session
|
|
92
94
|
|
|
93
|
-
You can also authenticate
|
|
95
|
+
You can also authenticate by creating a user session using the username and
|
|
94
96
|
password of an active user. If the user is an administrator, the session will have full access to
|
|
95
|
-
|
|
97
|
+
all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
|
|
96
98
|
user can access, and no access will be granted to site administration functions.
|
|
97
99
|
|
|
98
|
-
|
|
100
|
+
Sessions use the exact same session timeout settings as web interface sessions. When a
|
|
99
101
|
session times out, simply create a new session and resume where you left off. This process is not
|
|
100
|
-
automatically handled by SDKs because we do not want to store password information in memory without
|
|
102
|
+
automatically handled by our SDKs because we do not want to store password information in memory without
|
|
101
103
|
your explicit consent.
|
|
102
104
|
|
|
103
105
|
#### Logging In
|
|
@@ -136,6 +138,8 @@ await Session.destroy();
|
|
|
136
138
|
|
|
137
139
|
## Configuration
|
|
138
140
|
|
|
141
|
+
Global configuration is performed by calling methods on the `Files` object.
|
|
142
|
+
|
|
139
143
|
### Configuration Options
|
|
140
144
|
|
|
141
145
|
#### Base URL
|
package/_VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
1.2.
|
|
1
|
+
1.2.192
|
package/lib/Files.js
CHANGED
|
@@ -11,7 +11,7 @@ var endpointPrefix = '/api/rest/v1';
|
|
|
11
11
|
var apiKey;
|
|
12
12
|
var baseUrl = 'https://app.files.com';
|
|
13
13
|
var sessionId = null;
|
|
14
|
-
var version = '1.2.
|
|
14
|
+
var version = '1.2.192';
|
|
15
15
|
var userAgent = "Files.com JavaScript SDK v".concat(version);
|
|
16
16
|
var logLevel = _Logger.LogLevel.INFO;
|
|
17
17
|
var debugRequest = false;
|
package/package.json
CHANGED
package/src/Files.js
CHANGED