conduit authcommand line tool creates OAuth 2.0 client application identifiers and inserts them into an application's database. To use this tool, you must use
ManagedAuthDelegate<T>and your database must be contain the tables to support it (see this guide for more details).
conduit/managed_auth. Authenticating clients must provide their client ID (and client secret, if applicable) in the Authorization header when requesting access tokens.
com.food_app.mobilemay be a client identifier for the mobile applications for some 'Food App'.
connectoption identifies the database for the application, which this tool will connect to and insert a record into the
ManagedAuthClientdatabase table. The identifier is provided through the
Authorizer.basic), the client secret is omitted from the authorization header. The string to base64 encode is
clientID:, where the colon (
:) is required. For example, to generate an authorization header in Dart for a public client:
AuthCodeController), a client must have a redirect URI. This is the URI that an authenticating user's browser will be redirected to after entering their username and password. A client must be a confidential client to have a redirect URI.
conduit auth set-scope:
conduitcommands that send commands to a database, the
connectoption can be replaced by a
database.yamlfile in the project directory with the following format: