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

[Feature Request] Hiding Sensitive Inputs #3410

Open
jamesburns-rts opened this issue Jun 13, 2024 · 1 comment
Open

[Feature Request] Hiding Sensitive Inputs #3410

jamesburns-rts opened this issue Jun 13, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request long-term

Comments

@jamesburns-rts
Copy link

I would like to be able to pass sensitive parameters into the flow in a way they are not included in logging or tracing. Is this already possible?

My setup and situation

  • We're developing a flow through the VSCode plugin and then deploying it to an Azure AI Studio endpoint.
  • We need to call an API on the user's behalf using a JWT retrieved through our UI
  • We're currently passing the JWT through a flow input, which means we cannot:
    • enable tracing since it would include the JWT for any tool that accepts it
    • enable INFO logging because it also logs the tool arguments
    • enable recording of model inputs through azure

Possible solutions

  • Allow marking inputs as secret or private and prevent logging from that
  • Allow access of the original HTTP request being made so I can access extra body parameters or headers

Alternatives I've considered

  • a crazy encryption scheme
  • making all API calls through the UI instead of in the flow and having the UI re-call the prompt flow endpoint
@jamesburns-rts jamesburns-rts added the enhancement New feature or request label Jun 13, 2024
@0mza987
Copy link
Contributor

0mza987 commented Jun 14, 2024

It's rare and generally not recommentded to pass secrects as inputs in the request. Prompt flow does not have short-term plan to support this feature ask.

Please consider the workaround to encode the jwt first and decode inside the flow when you need to call the external API.

@0mza987 0mza987 self-assigned this Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request long-term
Projects
None yet
Development

No branches or pull requests

3 participants