... | @@ -50,7 +50,7 @@ Note that prefab OAuth tokens are usually issued for longer validity periods (th |
... | @@ -50,7 +50,7 @@ Note that prefab OAuth tokens are usually issued for longer validity periods (th |
|
|
|
|
|
The `pepcli` utility's general flags can be used to indicate how to connect to and [enroll with](#authentication-and-enrollment) the PEP system:
|
|
The `pepcli` utility's general flags can be used to indicate how to connect to and [enroll with](#authentication-and-enrollment) the PEP system:
|
|
|
|
|
|
- `--client-working-directory` specifies a directory containing configuration files specifying how to connect to PEP's servers. If not specified, these configuration files are assumed to be located in the directory containing the `pepcli` executable file.
|
|
- `--client-working-directory` specifies a directory containing configuration files specifying how to connect to PEP's servers. If not specified, these configuration files are assumed to be located in the directory containing the `pepcli` executable file. Users of PEP `client` Docker images should specify a `--client-working-directory /config` to use the configuration files included in the image.
|
|
- `--client-config-name` specifies the name of the main (client) configuration file. If not specified, the file is assumed to be named `ClientConfig.json`.
|
|
- `--client-config-name` specifies the name of the main (client) configuration file. If not specified, the file is assumed to be named `ClientConfig.json`.
|
|
- `--oauth-token` specifies an OAuth token to be used for [enrollment](Access-control#enrollment), or the path to a file containing such an OAuth token. If not specified, the user is assumed to [have been enrolled](#enrollment) prior to `pepcli`'s invocation, e.g. by means of the `pepLogon` utility.
|
|
- `--oauth-token` specifies an OAuth token to be used for [enrollment](Access-control#enrollment), or the path to a file containing such an OAuth token. If not specified, the user is assumed to [have been enrolled](#enrollment) prior to `pepcli`'s invocation, e.g. by means of the `pepLogon` utility.
|
|
|
|
|
... | | ... | |