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
As opposed to the other plugins, this plugin is NOT stateless (due to the nature of OpenID Connect using any other
462
-
flow than "Implicit Flow"). However, the frontend supports using a MongoDB instance as its backend storage, so as long
462
+
flow than "Implicit Flow"). However, the frontend supports using a MongoDB or Redis instance as its backend storage, so as long
463
463
that's reachable from all machines it should not be a problem.
464
464
465
465
The configuration parameters available:
466
466
* `signing_key_path`: path to a RSA Private Key file (PKCS#1). MUST be configured.
467
-
* `db_uri`: connection URI to MongoDB instance where the data will be persisted, if it's not specified all data will only
467
+
* `db_uri`: connection URI to MongoDB or Redis instance where the data will be persisted, if it's not specified all data will only
468
468
be stored in-memory (not suitable for production use).
469
-
*`client_db_uri`: connection URI to MongoDB instance where the client data will be persistent, if it's not specified the clients list will be received from the `client_db_path`.
469
+
*`client_db_uri`: connection URI to MongoDB or Redis instance where the client data will be persistent, if it's not specified the clients list will be received from the `client_db_path`.
470
470
* `client_db_path`: path to a file containing the client database in json format. It will only be used if `client_db_uri` is not set. If `client_db_uri` and `client_db_path` are not set, clients will only be stored in-memory (not suitable for production use).
471
471
* `sub_hash_salt`: salt which is hashed into the `sub` claim. If it's not specified, SATOSA will generate a random salt on each startup, which means that users will get new `sub` value after every restart.
472
472
*`provider`: provider configuration information. MUST be configured, the following configuration are supported:
473
473
*`response_types_supported` (default: `[id_token]`): list of all supported response types, see [Section 3 of OIDC Core](http://openid.net/specs/openid-connect-core-1_0.html#Authentication).
474
474
*`subject_types_supported` (default: `[pairwise]`): list of all supported subject identifier types, see [Section 8 of OIDC Core](http://openid.net/specs/openid-connect-core-1_0.html#SubjectIDTypes)
475
475
*`scopes_supported` (default: `[openid]`): list of all supported scopes, see [Section 5.4 of OIDC Core](http://openid.net/specs/openid-connect-core-1_0.html#ScopeClaims)
476
476
*`client_registration_supported` (default: `No`): boolean whether [dynamic client registration is supported](https://openid.net/specs/openid-connect-registration-1_0.html).
477
-
If dynamic client registration is not supported all clients must exist in the MongoDB instance configured by the `db_uri`in the `"clients"` collection of the `"satosa"` database.
477
+
If dynamic client registration is not supported all clients must exist in the MongoDB or Redis instance configured by the `db_uri`in the `"clients"` collection of the `"satosa"` database.
478
478
The registration info must be stored using the client id as a key, and use the parameter names of a [OIDC Registration Response](https://openid.net/specs/openid-connect-registration-1_0.html#RegistrationResponse).
479
479
*`authorization_code_lifetime`: how long authorization codes should be valid, see [default](https://github.com/IdentityPython/pyop#token-lifetimes)
480
480
*`access_token_lifetime`: how long access tokens should be valid, see [default](https://github.com/IdentityPython/pyop#token-lifetimes)
0 commit comments