How to set up custom header for Azure Service Bus Message in Azure AD B2C Custom Policy?

Nilam Patel 0

Hello,

I am currently working on an Azure AD B2C custom policy and need to send a message to Azure Service Bus with a custom header. Specifically, I need to set the BrokerProperties.ScheduledEnqueueTimeUtc header while sending the message.

Here is the TechnicalProfile configuration I am using:

<DisplayName>Send Service Bus Message</DisplayName>

<Item Key="ServiceUrl">serviceUrl</Item>

<Item Key="AuthenticationType">ApiKeyHeader</Item>

<Item Key="ClaimUsedForRequestPayload">serviceBusMessage</Item>

</Metadata>

</CryptographicKeys>

</InputClaims>

</OutputClaims>

</TechnicalProfile>

This flow works, but it does not set the custom header BrokerProperties.ScheduledEnqueueTimeUtc. If I try the same request with Postman, it works correctly by passing the custom header BrokerProperties with the value {"ScheduledEnqueueTimeUtc":"Mon, 27 Jan 2025 12:57:20 GMT"}.

Thanks in advance

Khadeer Ali 2,770 Reputation points Microsoft Vendor

2025-01-27T15:45:12.77+00:00

@Nilam Patel ,

Welcome to Microsoft Q&A Platform!

Thanks for reaching out.

I see you tried setting it directly in the metadata of the configuration. That's a good first thought, but unfortunately, that part is only for settings that don't change. To set a custom header like BrokerProperties where the value might be different each time, you actually need to create a separate piece of data called a 'claim' that holds the header's information (in a specific format called JSON). Then, you tell B2C to send that claim as a header when it talks to the Service Bus. It's a bit of a workaround, but it's how B2C handles these dynamic headers.
Nilam Patel 0 Reputation points

2025-01-28T08:15:53.3766667+00:00

@Khadeer Ali Thank you for the suggestion. How to send claim as a header? Because I need to send claim as body as well.

Thanks in advance.
Khadeer Ali 2,770 Reputation points Microsoft Vendor

2025-01-30T17:48:29.1433333+00:00

@Nilam Patel ,

You're absolutely right to ask! It's a good point that you need the claim value in both the header and the body. B2C handles headers a little differently, so we can't directly reuse the same claim for both at the same time.

1 answer

Jay Rao 0 Reputation points

2025-01-27T15:54:24.5566667+00:00
As mentioned by Khadeer Ali, indeed that would be a workaround. Meanwhile, to what you ask specifically a sample example to try could also be this.
<TechnicalProfile Id="SendServiceBusMessage">

<DisplayName>Send Service Bus Message</DisplayName>

<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.RestfulProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />

<Metadata>

<Item Key="ServiceUrl">serviceUrl</Item> <Item Key="SendClaimsIn">Header</Item> <Item Key="AuthenticationType">ApiKeyHeader</Item> <Item Key="HttpMethod">POST</Item>

</Metadata>

<CryptographicKeys>

<Key Id="Authorization" StorageReferenceId="TokenKey" />

</CryptographicKeys>

<InputClaims>

 <InputClaim ClaimTypeReferenceId="serviceBusMessage" DefaultValue='{"enable": false, "identityObjectId":"id"}' AlwaysUseDefaultValue="true" />  <InputClaim ClaimTypeReferenceId="ScheduledEnqueueTimeUtc" PartnerClaimType="BrokerProperties.ScheduledEnqueueTimeUtc" DefaultValue="Mon, 27 Jan 2025 12:57:20 GMT" AlwaysUseDefaultValue="true" />

</InputClaims>

<OutputClaims>

<OutputClaim ClaimTypeReferenceId="statusCode" />

</OutputClaims>

</TechnicalProfile>
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to set up custom header for Azure Service Bus Message in Azure AD B2C Custom Policy?

1 answer

Your answer