fix: treat nil enabled_clients as enabled for all applications

[davidlovas]

Bug

auth0 users create fails with "There are currently no active database or passwordless connections to choose from" when a connection has enabled_clients: null (the default, meaning enabled for all applications).

Root cause

GetEnabledClients() returns nil when enabled_clients is null in the API response. In Go, len(nil) == 0 evaluates to true, so the CLI treats connections enabled for all apps identically to connections explicitly disabled (empty slice).

Fix

Distinguish between nil (all apps, no restriction) and empty slice (explicitly disabled):

// Before
if len(connection.GetEnabledClients()) == 0 {

// After
if enabledClients := connection.GetEnabledClients(); enabledClients != nil && len(enabledClients) == 0 {

Applied to all 3 occurrences in internal/cli/users.go:

• createUserCmd() (line 407)
• importUsersCmd() (line 897)
• databaseAndPasswordlessConnectionOptions() (line 999)

Tested

Built the patched CLI locally and verified against a tenant with enabled_clients: null on the Username-Password-Authentication connection:

Command	Stock CLI (1.31.0)	Patched CLI
auth0 api post "users" --data '{...}'	Succeeds	Succeeds
auth0 users create -c "Username-Password-Authentication" ...	Fails	Succeeds

Same connection, same tenant — the Management API works, the users create wrapper does not.

Environment

• CLI version: 1.31.0 (also reproduced on 1.29.0)
• OS: macOS (Darwin, arm64)
• Connection: Username-Password-Authentication with enabled_clients: null

[ramya18101]

Hello @davidlovas ,

Thanks for raising the PR, We'll look into it and get back soon!