Clean way to create user and issue jwt token?

Currently i have an AuthenticationController which listens on post registration. This registration method, stores the user and create a jwt token.

    [HttpPost("registration")]
    public async Task<IActionResult> Registration([FromBody] RegistrationViewModel model)
    {
       if (!ModelState.IsValid)
           return BadRequest(new { code = "ModelNotValid", description = "Model is not valid." });
       
       if (_userService.UserNameTaken(model.UserName))
           return BadRequest(new { code = "UserNameTaken", description = $"The User Name 
                {model.UserName} is taken." });
       
       var identityResult = await _userService.CreateUserAsync(model);
       
       if (!identityResult.Succeeded)
           return BadRequest(identityResult.Errors);
       
       var user = _userService.GetUserByUserName(model.UserName);
       int validityDurationInHours = 3;
       string token = _jwtService.GenerateJwtToken(user, await _userService.GetUserRolesAsync(user), 
           validityDurationInHours);
        
        return Ok(new { code = "RegistrationSuccess", auth_token = token });
    }

But now i would like to refactor the code, so there would be a UsersController which saves the user and i am not sure if i should generate the jwt token in the same method as it is done now.

So i what i see as a way is when the user registers on client side it sends the data to the backend, if it was correct than the client will be notifed, which than redirects user to the login page. But i feel unnecesarry the redirection, the user data was correct so it should get the jwt token straigth away. But i am unsure that the issueing the token should be done by the userscontroller default post method, which saves the user.

The other way i see is when the user is saved the backend notifies the client and than the client create a new request to the backend to issue the token. But then the request feels unnecessary.