[StepDocumentation("Sets the 'x-upn' header on outgoing messages to the current user's UPN.")]classSetUsernameOutgoingStep:IOutgoingStep{publicTaskProcess(OutgoingStepContextcontext,Func<Task>next){varupn=ClaimsPrincipal.Current?.FindFirst(ClaimTypes.Upn)?.Value;if(upn!=null){varmessage=context.Load<Message>();varheaders=message.Headers;headers["x-upn"]=upn;}returnnext();}}

[Test]publicasyncTaskVerifyUpnHeaderIsSet(){// this is the UPNvarupn=Guid.NewGuid().ToString();// establish identity with UPN claimvarclaimsIdentity=newClaimsIdentity(new[]{newClaim(ClaimTypes.Upn,upn),});ClaimsPrincipal.ClaimsPrincipalSelector=()=>newClaimsPrincipal(claimsIdentity);// create one-way clientusing(varactivator=newBuiltinHandlerActivator()){varnetwork=newInMemNetwork();varbus=Configure.With(activator).Transport(t=>t.UseInMemoryTransportAsOneWayClient(network)).Options(o=>o.Decorate<IPipeline>(c=>{varpipeline=c.Get<IPipeline>();varstep=newSetUsernameOutgoingStep();returnnewPipelineStepInjector(pipeline).OnSend(step,PipelineRelativePosition.Before,typeof(AssignDefaultHeadersStep));})).Options(o=>o.LogPipeline(verbose:true)).Start();// create destination queuenetwork.CreateQueue("dst-queue");// send string message to destination queueawaitbus.Advanced.Routing.Send("dst-queue","hej med dig");// retrieve message that was sentvarmessage=network.GetNextOrNull("dst-queue");Assert.That(message,Is.Not.Null,"Expected to receive a message");Assert.That(message.Headers,Contains.Key("x-upn").And.ContainValue(upn));}}

------------------------------------------------------------------------------Message pipelines------------------------------------------------------------------------------Send pipeline:    RebusWikiCodeSamples.SetUsernameOutgoingStep        Sets the 'x-upn' header on outgoing messages to the current        user's UPN.    Rebus.Pipeline.Send.AssignDefaultHeadersStep        Assigns these default headers to the outgoing message:                1) a new GUID as the 'rbs2-msg-id' header (*).                2) a 'rbs2-return-address' (unless the bus is a one-way        client) (*).                3) a 'rbs2-senttime' with the current time.                4) 'rbs2-msg-type' with the message's simple assembly-qualified        type name (*).                (*) Unless explicitly set to something else    Rebus.Pipeline.Send.FlowCorrelationIdStep        Sets the 'rbs2-corr-id' header of the outgoing message        to one of the following three things:                1) The correlation ID of the message currently being handled.        2) The message ID of the message currently being handled.        3) The message's own message ID.    Rebus.Pipeline.Send.AutoHeadersOutgoingStep        If the outgoing message type has [HeaderAttribute(...,        ...)] on it, the found headers will automatically        be picked up and added to the outgoing message.                Headers already on the message will not be overwritten.    Rebus.Pipeline.Send.SerializeOutgoingMessageStep        Serializes the outgoing message using the configured        serializer, storing the resulting transport message back        to the context.    Rebus.Pipeline.Send.ValidateOutgoingMessageStep        Checks the consistency of the outgoing message    Rebus.Pipeline.Send.SendOutgoingMessageStep        Final step that uses the current transport to send the transport        message found in the context to all addresses found by looking        up the DestinationAddress object from the context.Receive pipeline:    Rebus.Retry.Simple.SimpleRetryStrategyStep        Wraps the invocation of the entire receive pipeline in an exception        handler, tracking the number of times the received message        has been attempted to be delivered.                If the maximum number of delivery attempts is reached,        the message is moved to the error queue.    Rebus.Retry.FailFast.FailFastStep        Checks if a message has failed with specific exceptions        and marks it as "failed too many times". This allows the SimpleRetryStrategyStep        to move it to the error queue.    Rebus.Pipeline.Receive.HandleDeferredMessagesStep        If the incoming message should not be handled now, this step        saves the message until it is time to deliver the message.                This is done by checking if the incoming message has a 'rbs2-deferred-until'        header with a desired time to be delivered.    Rebus.DataBus.ClaimCheck.HydrateIncomingMessageStep        Incoming step that 'hydrates' big messages, if the payload        was stored as a data bus attachment.    Rebus.Pipeline.Receive.DeserializeIncomingMessageStep        Deserializes the current transport message using the configured        serializer, saving the deserialized message back to the context.    Rebus.Pipeline.Receive.HandleRoutingSlipsStep        If the message being handled is a routing slip with an itinerary,        this step ensures that the routing slip is forwarded        to the next destination.    Rebus.Pipeline.Receive.ActivateHandlersStep        Looks at the incoming message and decides how to handle        it. A HandlerInvokers object is saved to the context to be        invoked later.    Rebus.Sagas.LoadSagaDataStep        Looks at the handler invokers in the context and sees if there's        one or more saga handlers in there.                If that's the case, relevant saga data is loaded/created,        and the rest of the pipeline gets invoked.                Afterwards, all the created/loaded saga data is updated        appropriately.    Rebus.Pipeline.Receive.DispatchIncomingMessageStep        Gets all the handler invokers from the current context        and invokes them in order.                Please note that each invoker might choose to ignore the invocation        internally.                If no invokers were found, a RebusApplicationException        is thrown.------------------------------------------------------------------------------