@@ -288,9 +288,9 @@ remain available as described at the start of the `Configuration`_ section.
288
288
| Secret value employed to encrypt user authentication tokens.
289
289
| **Important Note:**
290
290
| Changing this value at a later time will cause previously created user tokens to be invalidated.
291
- It is **strongly ** recommended to change this value before proceeding to user accounts and permissions creation
292
- in your `Magpie` instance.
293
- | (Default: ``"seekrit"`` )
291
+ This value **MUST ** be defined before starting the application in order to move on to user accounts and permissions
292
+ creation in your `Magpie` instance. The application will quit with an error if this value cannot be found .
293
+ | (Default: None )
294
294
295
295
- | ``MAGPIE_COOKIE_NAME ``
296
296
| Identifier of the cookie that will be used for reading and writing in the requests from login and for
@@ -303,15 +303,25 @@ remain available as described at the start of the `Configuration`_ section.
303
303
304
304
- | ``MAGPIE_ADMIN_USER ``
305
305
| Name of the default 'administrator' generated by the application.
306
- | **Note :**
307
- | This user is required for initial launch of the application to avoid being 'looked out' as routes for creating new
306
+ | **Important Notes :**
307
+ | This user is required for initial launch of the application to avoid being 'locked out' as routes for creating new
308
308
users require administrative permissions and access rights. It should be used as a first login method to setup other
309
- accounts. It will also be used by other `Magpie` internal operations such as service synchronization and setup
310
- during the application startup. If this user is missing, it is automatically re-created on following start.
309
+ accounts. It is afterwards recommended to employ other user accounts with ``MAGPIE_ADMIN_GROUP`` membership to
310
+ accomplish administrative management operations.
311
+ | This value **MUST** be defined before starting the application in order to move on any other operation in your
312
+ `Magpie` instance. The application will quit with an error if this value cannot be found. Also, no defaults are
313
+ applied to motivate the developer to configured new instances with server-specific and strong credentials.
314
+ | If this user is missing, it is automatically recreated on following start. The best way to invalidate this user's
315
+ credentials is therefore to completely remove its entry it from the database so it gets regenerated from updated
316
+ configuration values. Note also that modifying this value without actually updating the user entry in the database
317
+ could cause other operations to fail drastically since this special user will be employed by other `Magpie` internal
318
+ operations such as service synchronization and setup during the application startup.
311
319
| (Default: ``"admin"``)
312
320
313
321
- | ``MAGPIE_ADMIN_PASSWORD ``
314
322
| Password of the default 'administrator' generated by the application.
323
+ | **Important Notes:**
324
+ | This parameter is required in order for the `Magpie` instance to start. See details in above ``MAGPIE_ADMIN_USER``.
315
325
| (Default: ``"qwerty"``)
316
326
317
327
- | ``MAGPIE_ADMIN_EMAIL ``
@@ -326,7 +336,7 @@ remain available as described at the start of the `Configuration`_ section.
326
336
higher level permissions on this group to ease the management process of granted access to all their members.
327
337
| (Default: ``"administrators"``)
328
338
329
- - | ``MAGPIE_ADMIN_PERMISSION ``
339
+ - | ``MAGPIE_ADMIN_PERMISSION `` [constant]
330
340
| Name of the permission used to represent highest administration privilege in the application.
331
341
| Except for some public routes, most API and UI paths will require the user to have this permission (either with
332
342
direct permission or by inherited group permission) to be granted access to view and edit content.
@@ -372,7 +382,7 @@ remain available as described at the start of the `Configuration`_ section.
372
382
| This value should not be greater then the token length used to identify a user to preserve some utility behaviour.
373
383
| (Default: ``64``)
374
384
375
- - | ``MAGPIE_LOGGED_USER ``
385
+ - | ``MAGPIE_LOGGED_USER `` [constant]
376
386
| Keyword used to define route resolution using the currently logged in user. This value allows, for example,
377
387
retrieving the user details of the logged user with ``GET /users/${MAGPIE_LOGGED_USER}`` instead of having to
378
388
find explicitly the ``GET /users/<my-user-id>`` variant. User resolution is done using the authentication cookie
@@ -384,7 +394,7 @@ remain available as described at the start of the `Configuration`_ section.
384
394
unauthorized response if using is ID in the path if he doesn't have administrator privilege.
385
395
| (Default: ``"current"``)
386
396
387
- - | ``MAGPIE_DEFAULT_PROVIDER ``
397
+ - | ``MAGPIE_DEFAULT_PROVIDER `` [constant]
388
398
| Name of the provider used for local login. This represents the identifier that will be set to define who to
389
399
differentiate between a local sign-in procedure and a dispatched one to one of the known `External Providers`_.
390
400
| *The default is the value of the internal package used to manage user permissions.*
0 commit comments