Connect to Azure Managed Redis
Learn how to authenticate to an Azure Managed Redis (AMR) database
The go-redis-entraid
package
lets you authenticate your app to
Azure Managed Redis (AMR)
using Microsoft Entra ID.
You can authenticate using a system-assigned or user-assigned
managed identity
or a service principal,
letting go-redis-entraid
fetch and renew the authentication tokens for you automatically.
Install
Install go-redis
if you
have not already done so. Note that go-redis-entraid
requires go-redis
v9.9.0 or above, so you should upgrade if you
are using an earlier version.
Install go-redis-entraid
with the following command:
go get github.com/redis/go-redis-entraid
Create a StreamingCredentialsProvider
instance
The StreamingCredentialsProvider
interface defines methods
to provide credentials for authentication. Use an object that
implements this interface to obtain the authentication credentials you
need when you connect to Redis. See the sections below to learn how
to create the StreamingCredentialsProvider
instances for AMR
using the factory functions that go-redis-entraid
provides.
StreamingCredentialsProvider
for a service principal
Use the NewConfidentialCredentialsProvider()
factory function to create a
StreamingCredentialsProvider
that authenticates to AMR using a
service principal (see the
Microsoft documentation to learn more about service principals).
You will need the following details of your service principal to make the connection:
- Client ID
- Client secret
- Tenant ID
Use an AuthorityConfiguration
instance to pass the tenant ID.
This type has the following fields:
AuthorityType
: This should have one of the valuesidentity.AuthorityTypeDefault
("default")identity.AuthorityTypeMultiTenant
("multi-tenant")identity.AuthorityTypeCustom
("custom")
TenantID
: Pass your tenant ID string here, or use "common" for a multi-tentant application.Authority
: Custom authority URL. This is only required if you specifiedAuthorityTypeCustom
in theAuthorityType
field.
The example below shows how to import the required modules and call
NewConfidentialCredentialsProvider()
:
import (
"github.com/redis-developer/go-redis-entraid/entraid"
"github.com/redis-developer/go-redis-entraid/identity"
...
)
.
.
provider, err := entraid.NewConfidentialCredentialsProvider(
entraid.ConfidentialCredentialsProviderOptions{
ConfidentialIdentityProviderOptions: identity.ConfidentialIdentityProviderOptions{
ClientID: "<your-azure-client-id>",
ClientSecret: "<your-azure-client-secret>",
CredentialsType: identity.ClientSecretCredentialType,
Authority: identity.AuthorityConfiguration{
AuthorityType: identity.AuthorityTypeDefault,
TenantID: "<your-azure-tenant-id>",
},
},
},
)
StreamingCredentialsProvider
for a managed identity
Use the NewManagedIdentityCredentialsProvider()
function to create a
StreamingCredentialsProvider
that authenticates to AMR using a
managed identity (see the
Microsoft documentation to learn more about managed identities).
The example below shows how to import the required modules and call
NewManagedIdentityCredentialsProvider()
.
Pass identity.SystemAssignedIdentity
or identity.UserAssignedIdentity
as the ManagedIdentityType
parameter.
import (
"github.com/redis-developer/go-redis-entraid/entraid"
"github.com/redis-developer/go-redis-entraid/identity"
...
)
.
.
provider, err := entraid.NewManagedIdentityCredentialsProvider(
entraid.ManagedIdentityCredentialsProviderOptions{
ManagedIdentityProviderOptions: identity.ManagedIdentityProviderOptions{
ManagedIdentityType: identity.UserAssignedObjectID,
UserAssignedObjectID: "<your-user-assigned-client-id>",
},
},
)
Custom configuration
The examples above use a default configuration but you can also provide a custom
configuration using the TokenManagerOptions
field of CredentialsProviderOptions
:
options := entraid.CredentialsProviderOptions{
TokenManagerOptions: manager.TokenManagerOptions{
ExpirationRefreshRatio: 0.7,
LowerRefreshBounds: 10000,
RetryOptions: manager.RetryOptions{
MaxAttempts: 3,
InitialDelay: 1000 * time.Millisecond,
MaxDelay: 30000 * time.Millisecond,
BackoffMultiplier: 2.0,
IsRetryable: func(err error) bool {
return strings.Contains(err.Error(), "network error") ||
strings.Contains(err.Error(), "timeout")
},
},
},
}
You can then pass this configuration when you create the
StreamingCredentialsProvider
. The example below shows how to do this
with the NewManagedIdentityCredentialsProvider()
method:
provider, err := entraid.NewManagedIdentityCredentialsProvider(
entraid.ManagedIdentityCredentialsProviderOptions{
CredentialsProviderOptions: options,
ManagedIdentityProviderOptions: identity.ManagedIdentityProviderOptions{
ManagedIdentityType: identity.UserAssignedObjectID,
UserAssignedObjectID: "<your-user-assigned-client-id>",
},
},
)
The fields of TokenManagerOptions
are explained below:
ExpirationRefreshRatio
: Afloat
value representing the fraction of a token's lifetime that should elapse before attempting to refresh it. For example, a value of 0.75 means that you want to refresh the token after 75% of its lifetime has passed.LowerRefreshBounds
: The minimum amount of the token's lifetime (in milliseconds) remaining before attempting to refresh, regardless of theexpirationRefreshRatio
value. Set this to zero if you want the refresh time to depend only onexpirationRefreshRatio
.RetryOptions
: This object specifies how to retry a token request after failure. The available options are:MaxAttempts
: The maximum number of times to retry a token request The default value is 3.InitialDelay
: The initial delay between retries in milliseconds. This will be modified during successive attempts by theBackoffMultiplier
value (see below). The default is 1000ms.BackoffMultiplier
: The factor by which theInitialDelay
is multiplied between attempts, following an exponential backoff strategy. The default multiplier is 2.0.IsRetryable
: A function that receives anerror
parameter and returns a booleantrue
result if an attempt that failed with that error is retryable andfalse
otherwise. Use this to implement your own custom logic to decide which errors should be retried.
Connect
When you have created your StreamingCredentialsProvider
instance, you are ready to
connect to AMR.
The example below shows how to pass the instance as a parameter to the standard
NewClient()
connection method. It also illustrates how to use
os.Getenv()
to get the connection details
from environment variables rather than include their values in the code.
package main
import (
"context"
"fmt"
"log"
"os"
"strings"
"github.com/redis-developer/go-redis-entraid/entraid"
"github.com/redis/go-redis/v9"
)
func main() {
// Get required environment variables
redisEndpoint := os.Getenv("REDIS_ENDPOINT")
if redisEndpoint == "" {
log.Fatal(
"REDIS_ENDPOINT environment variable is required"
)
}
// Create credentials provider for system assigned identity
provider, err := entraid.NewManagedIdentityCredentialsProvider(
entraid.ManagedIdentityCredentialsProviderOptions{
ManagedIdentityProviderOptions: identity.ManagedIdentityProviderOptions{
ManagedIdentityType: identity.SystemAssignedIdentity,
},
}
)
if err != nil {
log.Fatalf("Failed to create credentials provider: %v", err)
}
// Create Redis client
client := redis.NewClient(&redis.Options{
Addr: redisEndpoint,
StreamingCredentialsProvider: provider,
})
defer client.Close()
// Test connection
ctx := context.Background()
if err := client.Ping(ctx).Err(); err != nil {
log.Fatalf("Failed to connect to Redis: %v", err)
}
log.Println("Connected to Redis!")
}
More information
See the go-redis-entraid
GitHub repository for full source code and more examples and details.