{"id":24610,"date":"2020-09-03T11:15:41","date_gmt":"2020-09-03T11:15:41","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=24610"},"modified":"2020-11-18T07:48:12","modified_gmt":"2020-11-18T07:48:12","slug":"impersonation-within-azure-function-or-custom-connector-when-using-aad-authentication","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/09\/impersonation-within-azure-function-or-custom-connector-when-using-aad-authentication\/","title":{"rendered":"Impersonation within Azure Function or Custom Connector when using AAD authentication"},"content":{"rendered":"

In the earlier blog posts, we discussed setting up an Azure function with AAD authentication<\/a> and then creating a custom connector for the Azure function that also requires AAD authentication to make a connection to the connector<\/a>.<\/p>\n

Given that the Azure function is configured for AAD authentication in the Authentication \/ Authorization section of the function as shown below<\/p>\n

\"Azure<\/a><\/p>\n

Now that we have provided for AAD authentication that requires a user login, it would be good if all operations are executed within the context of the same user.<\/p>\n

Within your Azure function, you can get the details of the logged-in user using the ClaimsPrincipal<\/a><\/p>\n

ClaimsPrincipal principal = req.HttpContext.User;<\/p>\n

if (principal.Identity != null)<\/p>\n

{<\/p>\n

log.LogInformation(“Claims identity ” + principal.Identity.Name);<\/p>\n

}<\/p>\n

if (principal.Claims != null)<\/p>\n

{<\/p>\n

foreach (Claim c in principal.Claims)<\/p>\n

{<\/p>\n

log.LogInformation(“CLAIM TYPE: ” + c.Type + “; CLAIM VALUE: ” + c.Value + “<\/br>”);<\/p>\n

}<\/p>\n

\u00a0}<\/p>\n

In the console, you can see all the claims returned<\/p>\n

\"Azure<\/a><\/p>\n

One of the claims returned is AADID<\/p>\n

\"Azure<\/a><\/p>\n

Read this specific claim value<\/p>\n

Claim claim = principal.Claims.FirstOrDefault(c => c.Type.Contains(“objectidentifier”));<\/p>\n

string aadobjid = “”;<\/p>\n

if (claim != null)<\/p>\n

{<\/p>\n

aadobjid = claim.Value;<\/p>\n

log.LogInformation(“aadobjid = ” + aadobjid);<\/p>\n

}<\/p>\n

Every CRM User that we create has an associated AADID stored along which is this objectid.<\/p>\n

Set this to the cds client object we have created for impersonation<\/p>\n

\/\/establish connection with CDS<\/p>\n

CdsServiceClient client = new CdsServiceClient(connectionString);<\/p>\n

if (!string.IsNullOrEmpty(aadobjid))<\/p>\n

{<\/p>\n

client.CallerAADObjectId = new Guid(aadobjid);<\/p>\n

}<\/p>\n

Do note if you run a WhoAmI request \u2013 it still returns the id of the original credentials used for establishing the connection.<\/p>\n

However, when you create a record, you will notice that the owner of the new record is the same user that had logged in to the connector.<\/p>\n","protected":false},"excerpt":{"rendered":"

In the earlier blog posts, we discussed setting up an Azure function with AAD authentication and then creating a custom connector for the Azure function that also requires AAD authentication to make a connection to the connector. Given that the Azure function is configured for AAD authentication in the Authentication \/ Authorization section of the\u2026 Read More: Impersonation within Azure Function or Custom Connector when using AAD\u2026 »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":24621,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,2088],"tags":[2070,2071,2089,545],"class_list":["post-24610","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-functions","category-custom-connector","tag-aad-authentication","tag-azure-function","tag-custom-connector","tag-dynamics-365-crm"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t