Skip to content

conductor whoami fails on OSS with 'no authentication configured' #16

@nthmost-orkes

Description

@nthmost-orkes

Problem

Running `conductor whoami` against a local OSS server returns an error:

```
Error: no authentication configured - please configure auth-token or auth-key/auth-secret
```

OSS Conductor has no authentication — this is by design. The command should either work without credentials on OSS (showing server URL, version, server type) or detect that the server is OSS and display a helpful message instead of an error.

As it stands, a new user who tries `conductor whoami` to confirm their setup is working gets an error that implies something is broken, when nothing is wrong.

Fix

  • Detect OSS server type and skip auth check
  • Return useful info: server URL, server version, server type

Affects

  • `conductor-oss/conductor-cli`

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: cliconductor-cli binary or templatescriticalSeriously impacts zero-to-one onboardingfix: codeFix requires a code change in a repo

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions