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

[gRPC] TLS enable/disable by variable #11489

Open
1 task done
Amoratinos opened this issue Nov 28, 2022 · 6 comments
Open
1 task done

[gRPC] TLS enable/disable by variable #11489

Amoratinos opened this issue Nov 28, 2022 · 6 comments
Assignees
Labels
feature product/api-client protocol/grpc Issues related to the gRPC protocol experience in Postman

Comments

@Amoratinos
Copy link

Is there an existing request for this feature?

  • I have searched the existing issues for this feature request and I know that duplicates will be closed

Is your feature request related to a problem?

Among different environment TLS settings can be different, e.g. Local development vs QA. As we use server reflection to trigger requests when we switch between different environments users have to be aware that they have to click on the 🔒 icon to change TLS settings.

Describe the solution you'd like

I'd like that TLS settings for gRPC requests could be enabled/disabled based on an environment setting.

Describe alternatives you've considered

No response

Additional context

No response

@codenirvana codenirvana added protocol/grpc Issues related to the gRPC protocol experience in Postman product/api-client labels Nov 28, 2022
@codenirvana codenirvana self-assigned this Nov 28, 2022
@kravchuk-rye
Copy link

Any updates on this? We really need this too!

@codenirvana
Copy link
Member

We are thinking of achieving this using URL schemes like grpc:// and grpcs:// in the server URL instead.
The scheme will override the TLS setting (🔒 icon).

Let me know if that unblocks your use case.

@kravchuk-rye
Copy link

Correct me if I'm wrong, this approach does not work just yet. This would unblock our case!

@cotzo
Copy link

cotzo commented Feb 27, 2023

+1 on this issue since it's blocking many developers working with grpc since mostly local dev is using non TLS and production is using TLS. thanks!

@abatolyg
Copy link

+1

This will be great to achieving this using URL schemes like grpc:// and grpcs:// in the server URL instead.
The scheme will override the TLS setting (🔒 icon).

Details:
We also have gRPC Service running on 2 environments - local machine and dev in cloud
For local env I send gRPC queries with TLS Disabled.
For dev cloud env i send gRPC queries with TLS Enabled.
I have 100 scripts
Each time I run all the scripts and switch from Local to DEV/Cloud environment
I need to manually Disable Enable for each request!
I do not want to DUPLICATE my collection and to keep the LOCAL and DEV environments version.
I want to be able to Enable/Disable TLS from script.

@jdgordon-eightcap
Copy link

@codenirvana

We are thinking of achieving this using URL schemes like grpc:// and grpcs:// in the server URL instead. The scheme will override the TLS setting (🔒 icon).

Let me know if that unblocks your use case.

Has this been implemented yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature product/api-client protocol/grpc Issues related to the gRPC protocol experience in Postman
Projects
None yet
Development

No branches or pull requests

6 participants