BerriAI/litellm · error · HTTPException

You are not authorized to regenerate this key

Error message

You are not authorized to regenerate this key

What it means

Error "You are not authorized to regenerate this key" thrown in BerriAI/litellm.

Source

Thrown at litellm/proxy/management_endpoints/key_management_endpoints.py:4995

            )

        # check if user has permission to regenerate key
        await TeamMemberPermissionChecks.can_team_member_execute_key_management_endpoint(
            user_api_key_dict=user_api_key_dict,
            route=KeyManagementRoutes.KEY_REGENERATE,
            prisma_client=prisma_client,
            existing_key_row=_key_in_db,
            user_api_key_cache=user_api_key_cache,
        )

        # check if user has ownership permission to regenerate key
        if not await can_modify_verification_token(
            key_info=_key_in_db,
            user_api_key_cache=user_api_key_cache,
            user_api_key_dict=user_api_key_dict,
            prisma_client=prisma_client,
        ):
            raise HTTPException(
                status_code=status.HTTP_403_FORBIDDEN,
                detail={"error": "You are not authorized to regenerate this key"},
            )

        if data is not None and (data.access_group_ids or data.object_permission is not None):
            regenerate_team_table: LiteLLM_TeamTableCachedObj | None = None
            if _key_in_db.team_id is not None:
                regenerate_team_table = await get_team_object(
                    team_id=_key_in_db.team_id,
                    prisma_client=prisma_client,
                    user_api_key_cache=user_api_key_cache,
                    check_db_only=True,
                )
            _regen_is_proxy_admin: Final = user_api_key_dict.user_role == LitellmUserRoles.PROXY_ADMIN.value
            TeamMemberPermissionChecks.enforce_member_can_assign_access_groups(
                user_api_key_dict=user_api_key_dict,
                team_table=regenerate_team_table,
                access_group_ids=data.access_group_ids,

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Authenticate as the key's owner, a team admin of the key's team, or a proxy admin.
2. Ask a proxy admin to regenerate the key for you.

When it happens

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

Common situations: See trigger scenarios.

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