The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
grafana/pkg/services/authz
Serge Zaitsev 694b9dfe50
Chore: Replace xorm.io/xorm imports (#104458)
3 weeks ago
..
proto/v1 UnifiedStorage: Rename Batch processing to Bulk (#101413) 3 months ago
rbac IAM: Add `datasources:query` support for using the authlib/authzservice (#104107) 4 weeks ago
zanzana Chore: Replace xorm.io/xorm imports (#104458) 3 weeks ago
README.md AuthZ: Introduce cloud mode (#96922) 6 months ago
rbac.go Provisioning: Use role based access when the target does not yet exist (#103862) 1 month ago
rbac_settings.go AuthZ: Make cache ttl configurable (#103769) 1 month ago
token_auth.go AuthZ: Make `NewGrpcTokenAuth` public (#101352) 3 months ago
wireset.go
zanzana.go Zanzana: Fix OpenFGA HTTP server (#104088) 4 weeks ago

README.md

Authorization

This package contains the authorization server implementation.

Feature toggles

The following feature toggles need to be activated:

[feature_toggles]
authZGRPCServer = true
grpcServer = true

Configuration

To configure the authorization server and client, use the "authorization" section of the configuration ini file.

The remote_address setting, specifies the address where the authorization server is located (ex: server.example.org:10000).

The mode setting can be set to either cloud, grpc or inproc. When set to cloud (or grpc), the client will connect to the specified address. When set to inproc the client will use inprocgrpc (relying on go channels) to wrap a local instantiation of the server.

The listen setting determines whether the authorization server should listen for incoming requests. When set to true, the authorization service will be registered to the Grafana GRPC server.

The default configuration does not register the authorization service on the Grafana GRPC server and binds the client to it inproc:

[authorization]
remote_address = ""
listen = false
mode = "inproc"

Example

Here is an example to connect the authorization client to a remote grpc server.

[authorization]
remote_address = "server.example.org:10000"
listen = false
mode = "grpc"

Here is an example to register the authorization service on the Grafana GRPC server and connect the client to it through grpc.

app_mode = development

[authorization]
remote_address = "localhost:10000"
listen = true
mode = "grpc"

Here is an example to connect the authorization client to a remote grpc server and use access token authentication.

[environment]
stack_id = 11

[authorization]
remote_address = "server.example.org:10000"
mode = "cloud"
listen = false

[grpc_client_authentication]
token = "ReplaceWithToken"
token_exchange_url = "signing-server.example.org/path/to/signing"
token_namespace = "stacks-11"