Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MessageDrivenSubscriptionsConfigExtensions.SubscriptionAuthorizer lambda exposes IIncomingPhysicalMessageContext #3720

Open
johnsimons opened this issue Apr 29, 2016 · 2 comments

Comments

@johnsimons
Copy link
Member

The problem with this is that a user has access to a lot of things that I don't think make sense, eg:

endpointConfiguration.UseTransport<MsmqTransport>()
                .SubscriptionAuthorizer(context =>
                {
                    context.UpdateMessage(new byte[0]);
                    return true;
                });
@andreasohlund
Copy link
Member

Since the subscriptions are control messages should we only give them a readonly dictionary?

@danielmarbach danielmarbach modified the milestones: 7.0.0, Future Oct 26, 2016
@danielmarbach
Copy link
Contributor

We should probably only pass in IncomingMessage. The Incoming Message doesn't allow to update the body.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants