Service configuration allows Inigo’s users to apply fine-grianed authorization and access controls. Not all clients are the same; you may have authenticated and unauthenticated clients using your application. Using the access control capabilities of Inigo, you can enforce strong authorization controls depending on the context of your clients.
This section defines the format of Inigo’s
Service type configuration files. Fields marked as
required must be specified if the parent is defined.
| || ||No||Path to the Trace ID header.|
| || ||No||Path to a user profile header. For JWT headers, you can use |
| || ||No||Path to a user role header. For JWT headers, you can use |
| || ||No||Path to a user ID header. For JWT headers, you can use |
| || ||No||Path to the client version header.|
| || ||No (default: ||Interval (in seconds) to poll the GraphQL schema from the application.|
| || ||No (default: ||Interval (in seconds) to poll new configurations.|
| || ||No default ( ||Enable the exposure of the GraphQL |
| || ||No||Name of an anonymous profile.|
| || ||No||List of roles that are considered anonymous.|
| || ||No||Relative path to the filesystem location of your files containing GraphQL schemas. For example: |
| || ||No||List of |
| || ||No||Default action to take upon failure mode. Options: |
The example service configuration below shows how a service can be defined.
kind: Service name: demo label: starwars spec: path_user_profile: jwt.user_profile path_user_role: jwt.user_roles path_user_id: jwt.user_name anonymous_profile: guest anonymous_roles: - viewer polling_interval_schema: 300 polling_interval_profile: 2 enable_extensions_output: true reduce_extension_output: - trace failure_mode: query_only schema_files: - ../../schemas/prod.graphql