TextTarget is described as using API-key authentication even though it needs no credentials

Open Beginner friendly
#3,712 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@pcbeingused333 is already working on this.

Since Nov 1, 2026.

  • #3777 by @pcbeingused333 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Start with frontend/src/components/Config/CreateTargetDialog.tsx, especially the selected-target description noted in the issue, and trace where target authentication metadata comes from. Check the target metadata and related tests to see how authentication requirements are represented. Done means TextTarget is described as requiring no credentials rather than API-key authentication.

Written by the indexing model from the issue text.

Description

help wanted
Is your feature request related to a problem? Please describe.

The target dropdown/details describe local TextTarget as supporting API-key authentication, which misleads users into thinking credentials are required.

Describe the solution you'd like

Represent no-auth targets explicitly in target metadata and say that TextTarget requires no credentials.

Describe alternatives you've considered, if relevant

At minimum, avoid presenting API accepted auth_mode values as the target's credential requirements.

Additional context

Reproduction: open Registry > Targets > New Target, select TextTarget, and read the selected-target description; creating it without credentials succeeds while the description says Supported authentication: API key. Source: CreateTargetDialog.

Tested commit d3446e045960b5ebee4641aa70fdeb03af186587, PyRIT 1.2.0.dev0, offline local-backend/browser scope. Evidence: files/evidence/round2/texttarget-auth.png and target-types.json; these local paths are not attachments.

Dominant language
Python
Stars
4.7k
Forks
1k
Avg merge
2d 3h
Merged PRs (30d)
450

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/PyRIT

All issues in microsoft/PyRIT

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.