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

Pre-fill authorization settings form #7815

Open
mariusz-schimke opened this issue Dec 10, 2024 · 1 comment
Open

Pre-fill authorization settings form #7815

mariusz-schimke opened this issue Dec 10, 2024 · 1 comment

Comments

@mariusz-schimke
Copy link

Product

Nitro

Is your feature request related to a problem?

When accessing the Connection Settings in Nitro UI and navigating to the Authorization tab, users are required to manually specify authentication settings from scratch. Given that APIs commonly require authentication, this process involves either:

  • Generating a Bearer token externally and manually inputting it, or
  • Filling out the OAuth form, which includes multiple technical details that often vary across environments.

This can be cumbersome and error-prone, particularly when working with multiple environments.

The solution you'd like

It would be highly beneficial to allow pre-configuration of base authentication parameters within Nitro. This would enable users to:

  • Skip repetitive manual input for OAuth settings.
  • Obtain access tokens more easily, with minimal interaction and knowledge of technical parameters.

I reviewed the documentation for configuring Nitro in .NET but couldn't find any options for pre-filling authentication settings based on the application configuration. If such functionality already exists, I’d appreciate guidance on how to implement it.

If not, I’d kindly ask you to consider adding this feature to simplify the authentication workflow for users.

Thank you for considering this improvement. I think it would significantly enhance the usability of Nitro in API-driven workflows.

@michaelstaib
Copy link
Member

You can store the authentication details in an API node with an organization account. All your peers will than have the same auth settings available.

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

2 participants