[Auth0\SDK\Exception\CoreException] Invalid domain when trying to run unit tests with Codeception 3.1.0

[jmbantay]

Description

I am part of a team developing a Yii 2 web app, although I cannot disclose the nature of the web app. We use Auth0 for the log in function.

My current task is to create unit tests for a specific class in the web app. I am using Codeception for this. I created a simple test and tried to run it just to see if everything will go smoothly. My test:

<?php 
class OSSTest extends \Codeception\Test\Unit
{
    /**
     * @var \UnitTester
     */
    protected $tester;
    
    protected function _before()
    {
    }

    protected function _after()
    {
    }

    // tests
    public function testSomeFeature()
    {
        $this->assertTrue(true);

    }
}

When I run the test, i get the following exception:

[Auth0\SDK\Exception\CoreException] Invalid domain
#1  /home/.../vendor/auth0/auth0-php/src/Auth0.php:167
#2  /home/.../config/params.php:7
#3  /home/.../config/test.php:2
#4  /home/.../vendor/symfony/event-dispatcher/EventDispatcher.php:260
#5  /home/.../vendor/symfony/event-dispatcher/EventDispatcher.php:235
#6  /home/.../vendor/symfony/event-dispatcher/EventDispatcher.php:73

What could be the problem? I'm new to Auth0, so any help would be greatly appreciated.

Environment

• Version of Auth0-PHP used: 5.0.6
• Version of PHP used: 7.3.8
• Additional packages or frameworks used that might be relevant: Yii 2 (2.0.25), Codeception 3.1.0

[joshcanhelp]

@jmbantay - It sounds like you're trying to initialize the Auth0 class without a domain key in your configuration. Can you share the code that's doing that initialization? It could be that you have it set to an ENV value but don't have an .env file for your testing suite.

Here's an example of the correct way to initialize that:

https://auth0.com/docs/quickstart/webapp/php#configure-auth0-php-sdk

[joshcanhelp]

No activity

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.