Skip to content

gRPC:PipeSecurity for Named Pipes #35691

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

gRPC:PipeSecurity for Named Pipes #35691

wants to merge 6 commits into from

Conversation

wadepickett
Copy link
Contributor

@wadepickett wadepickett commented Jul 1, 2025 •
edited by github-actions bot
Loading

Fixes #31489

Added section and code example on Configuring PipeSecurity for Named Pipes.

Internal previews

📄 File 🔗 Preview link
aspnetcore/grpc/interprocess-namedpipes.md aspnetcore/grpc/interprocess-namedpipes

@wadepickett wadepickett self-assigned this Jul 1, 2025
@wadepickett wadepickett requested a review from JamesNK July 1, 2025 23:52
@wadepickett wadepickett marked this pull request as ready for review July 1, 2025 23:52
@JamesNK
Copy link
Member

JamesNK commented Jul 2, 2025

It's also possible to customize security using CreateNamedPipeServerStream API added in .NET 9: https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-9.0?view=aspnetcore-9.0#customize-kestrel-named-pipe-endpoints

CreateNamedPipeServerStream allows different security settings per-endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JamesNK JamesNK Awaiting requested review from JamesNK

Assignees

@wadepickett wadepickett

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

gRPC Inter-process: mention NamedPipeTransportOptions configuration of Pipe Security
2 participants
@wadepickett @JamesNK