Skip to main content

Azure SQL: Dependency Injection with EFCore 3.x for AAD Authentication


While we're trying to connect our client application (console, windows, or web application) using Azure SQL database its preferred to use access token-based AAD authentication. 

Per preferred practice to avoid NEW keyword to create objects we generally use dependency injection to create objects. 

To inject the DbContext using Entity Framework Core (3.x) we have an overridden method OnConfigure() which can be used to set up the UserSQLServer() configuration to create the SQL connection. But to use UseSqlServer extension of DbContextOptionBuilder we've to create the DbConnection (or SQLConnection) after opening the SQL-connection (conn.Open()). 

The problem with this approach is there is no option to dispose or close the SQL connection which we opened while creating the DbContext through DI. The below code demonstrates the general approach to achieve this.

 
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
	// if it's AAD authentication, then get the SQLConnection and set AccessToken every time
	//  in all other cases (WindowsAuth, other SQL auth...), we will go with regular EFCore userSqlServer configuration
	if (_sqlConfigValues.IsAADAuthEnabled)
	{
		var sqlConnection = _sqlConnectionHelper.GetSqlConnection(_sqlConfigValues);
		optionsBuilder.UseSqlServer(sqlConnection, option =>
		{
			option.CommandTimeout(_sqlConfigValues.CommandTimeoutInSeconds);
		}
		);
	}
	else
	{
		if (!optionsBuilder.IsConfigured)
		{
			var connectionString = _sqlConnectionHelper.GetSqlConnectionString(_sqlConfigValues);
			optionsBuilder.UseSqlServer(connectionString, option =>
			{
				option.CommandTimeout(_sqlConfigValues.CommandTimeoutInSeconds);
			}
		);
		}
	}
}
    

Your GetSqlConnection method will be something like this

  public SqlConnection GetSqlConnection(SqlConfigValues sqlConfigValues)
{
	var sqlConnectionString = GetSqlConnectionString(sqlConfigValues);	
	var sqlConnection = new SqlConnection(sqlConnectionString);

	// AAD auth then set the token
	if (sqlConfigValues.IsAADAuthEnabled)
	{
		var accessToken =_tokenFactory.GetDBAccessToken();
		sqlConnection.AccessToken = accessToken;
	}

	// let's open the connection
	sqlConnection.Open();

	return sqlConnection;
}
  

Your SQL ConfigValues class definition is something like this

  namespace YourNamespace.ConfigValues
{
    public class SqlConfigValues
    {
        public string DatabaseServer { get; private set; }

        public string DatabaseName { get; private set; }
        public int ConnectionRetryCount { get; private set; }
        public int CommandTimeoutInSeconds { get; private set; }
        public int ConnectionTimeoutInSeconds { get; private set; }

        public bool IsAADAuthEnabled { get; private set; }
        public bool IsWindowsAuthEnabled { get; private set; }

        //
        public string SqlUserName { get; private set; }
        public string SqlPassword { get; private set; }
    }
}
    

To resolve this issue, Opening the SQL-connection every time while creating the DB context object through DI, we can take the help of DbConnectionINterceptor like this. 

   public class AzureAuthInterceptor : DbConnectionInterceptor
    {
        private readonly ITokenFactory _tokenFactory;
        public AzureAuthInterceptor(ITokenFactory tokenFactory)
        {
            _tokenFactory = tokenFactory;
        }

        public override async Task ConnectionOpeningAsync(DbConnection connection, ConnectionEventData eventData, InterceptionResult result, CancellationToken cancellationToken = default)
        {
            if (!(connection is SqlConnection conn))
            {
                return result;
            }

            conn.AccessToken =  await _tokenFactory.GetDBAccessTokenAsync();
            
            return result;
        }
    }
    


And in your TokenFactory class and respective ITokenFactory

 

 public async Task GetDBAccessTokenAsync()
        {
            // it will use MSI 
            AzureServiceTokenProvider provider = new AzureServiceTokenProvider();
            var accessToken = await provider.GetAccessTokenAsync("https://database.windows.net/")
                .ConfigureAwait(false);

            return accessToken;
        }
  

Now in your Startup.cs, you can use something like this  

  services.AddDbContext((serviceProvider, options) =>
            {
                var sqlConnHelper = serviceProvider.GetService();
                var tokenFactory = serviceProvider.GetService();
                options.UseSqlServer(sqlConnHelper.GetSqlConnectionString(sqlConfigValues))   // here we're just passing the connection string not the SqlConnection object
                    .AddInterceptors(new AzureAuthInterceptor(tokenFactory));  // this code will take care of getting the accessToken when required.
            });
    


This code is tested with EFCore 3.1.8/7/6 versions. 


Comments

Popular posts from this blog

EFCore - Collate function

Search in SQL server query is generally case insensitive (by default or based on database level collation). Suppose we have an employees table with a row having first-name column value as "My-First-Name", so if we want to do the case-sensitive search we have to explicitly use the related collate: In EF 5 (currently in Release Candidate version [RC.2.20475.6]) Collate function got introduced which helps us to use our specific collation based search.  C# with EF5 code sample: var employeeCaseSensitiveSearch = _dbContext.Employees .Where(x => EF.Functions.Collate(x.FirstName, "Latin1_General_CS_AS") == "my-first-name") .FirstOrDefault(); A related database query will be something like this: T-SQL: Case sensitive search (use specific collation e.g.: Latin1_General_CS_AS) SELECT * FROM dbo.Employees AS e WHERE e.FirstName Collate Latin1_General_CS_AS = 'my-first-name' Some of the useful CSharp function which g...

Git - Update submodule

Sometimes in the large project when we separate it in different repositories we need to take reference of one repository in another where some the sub-module concepts. Now if we move our submodule to a different repository or renaming its repo-path then we've to also update the repository where this sub-module is getting referenced. Let's see how to update the git submodule.  Step-1: First clone the repo Step-2: Open git UI to create a new local branch from master  Step-3: Open git bash -- Now run below command to (remove submodules & add them):  -- Remove submodule git submodule deinit YOUR_FIRST_REPO git rm YOUR_FIRST_REPO git commit -m "Removed submodule YOUR_FIRST_REPO" rm -rf .git/modules/YOUR_FIRST_REPO -- Add submodule git submodule add <<..YOUR_FIRST_REPO git URL>> Step-4: All good, let's push our changes to the master

EFCore - Update command is not updating the underlying data

Why my update command using EFCore is not updating the underlying data in the database though in middle-tier code it's successful, not throwing any error? Let's try to get the root cause and how to solve this.  When creating the model class of related database object if the primary key name is Id then no need to explicitly mention the Key in ef-core OnModelCreating.  But if we've key name different from Id then we have to explicitly mention it in our OnModelCreating. Something like this:  entity.HasKey(c => new {c.CustId }); Assume in the database we've Customers table like this: CREATE TABLE [dbo].[Customers]( [CustId] [INT] IDENTITY(1,1) NOT NULL Primary Key, [FirstName] [VARCHAR](50) NULL ) Point to ponder: In the database table, column CustId is already defined as Primary key.  In EFCore model setup, it's up to us to configure the Key as (custId) or configure it as HasNoKey() Assume we've set our entity with Ha...