# AUTH_PROVIDER_AVAILABLE

**What it means.** This app has its own sign-in, but the platform already signs people in to a private app and tells the app who they are.

**What to do.** In a private app, remove the auth library and read the person from the x-uarpie-user-id, x-uarpie-user-email, x-uarpie-user-name and x-uarpie-user-role headers (or GET /_platform/me from browser code); the platform removes those headers from anything a visitor sends. A public app whose visitors are strangers keeps its own sign-in. This is a warning; deploy continues.

- HTTP status: 422
- Retryable after applying the fix: yes

Every failure from the CLI or an MCP tool has this shape:

```json
{
  "ok": false,
  "code": "AUTH_PROVIDER_AVAILABLE",
  "message": "This app has its own sign-in, but the platform already signs people in to a private app and tells the app who they are.",
  "fix": "In a private app, remove the auth library and read the person from the x-uarpie-user-id, x-uarpie-user-email, x-uarpie-user-name and x-uarpie-user-role headers (or GET /_platform/me from browser code); the platform removes those headers from anything a visitor sends. A public app whose visitors are strangers keeps its own sign-in. This is a warning; deploy continues.",
  "file": "<where to edit, when known>",
  "retryable": true,
  "docs": "https://docs.uarpie.app/errors/AUTH_PROVIDER_AVAILABLE"
}
```

Apply `fix` (edit `file` when it is given), then run the same command again.