BerriAI/litellm · error · ProxyException

Authentication Error, {e}

Error message

Authentication Error, {e}

What it means

The generic except-branch of /organization/add_member: a non-HTTPException failure (DB error, prisma failure, unexpected bug) is logged and re-raised as a ProxyException tagged auth_error with HTTP 500. It tells the client the member-add transaction failed server-side without leaking internals beyond str(e).

Source

Thrown at litellm/proxy/management_endpoints/organization_endpoints.py:1266

            updated_organization_memberships.append(updated_organization_membership)

        return OrganizationAddMemberResponse(
            organization_id=data.organization_id,
            updated_users=updated_users,
            updated_organization_memberships=updated_organization_memberships,
        )
    except Exception as e:
        verbose_proxy_logger.exception("Error adding member to organization: %s", e)
        if isinstance(e, HTTPException):
            raise ProxyException(
                message=getattr(e, "detail", f"Authentication Error({e})"),
                type=ProxyErrorTypes.auth_error,
                param=getattr(e, "param", "None"),
                code=getattr(e, "status_code", status.HTTP_500_INTERNAL_SERVER_ERROR),
            )
        elif isinstance(e, ProxyException):
            raise e
        raise ProxyException(
            message="Authentication Error, " + str(e),
            type=ProxyErrorTypes.auth_error,
            param=getattr(e, "param", "None"),
            code=status.HTTP_500_INTERNAL_SERVER_ERROR,
        )


async def find_member_if_email(user_email: str, prisma_client: PrismaClient) -> LiteLLM_UserTable:
    """
    Find a member if the user_email is in LiteLLM_UserTable
    """

    try:
        existing_user_email_row: Final[BaseModel] = await UserRepository(prisma_client).table.find_unique(
            where={"user_email": user_email}
        )
    except Exception:
        raise HTTPException(

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check the API key/credentials used for the request.
2. Check proxy server logs for the underlying auth error.

When it happens

Trigger: Thrown at litellm/proxy/management_endpoints/organization_endpoints.py:1266 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Authentication and authorization failures — expired tokens, bad credentials, and missing scopes.

AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18). Data as JSON: /api/errors/000d332a380fca93. Report an issue: GitHub.