-
Notifications
You must be signed in to change notification settings - Fork 956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unknow column id_token in authorize.php #361
Comments
The documentation represents the v1.3 version of the library. You've installed the development branch. Either switch to the stable tag, or add the id_token column to your AuthorizationCode data store — On Fri, Mar 28, 2014 at 10:42 AM, bashekking [email protected]
|
when I follow the install procedure and open the authorize.php page(/authorize.php?response_type=code&client_id=testclient&state=xyz) i get the following error
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 'id_token' in 'field list'' in /home/bas/development/codefined.com/oauth/www/oauth2-server-php/src/OAuth2/Storage/Pdo.php:181 Stack trace: #0 /home/bas/development/codefined.com/oauth/www/oauth2-server-php/src/OAuth2/Storage/Pdo.php(181): PDOStatement->execute(Array) #1 /home/bas/development/codefined.com/oauth/www/oauth2-server-php/src/OAuth2/ResponseType/AuthorizationCode.php(60): OAuth2\Storage\Pdo->setAuthorizationCode('11131b5f009e09d...', 'testclient', NULL, NULL, 1396023903, NULL) #2 /home/bas/development/codefined.com/oauth/www/oauth2-server-php/src/OAuth2/ResponseType/AuthorizationCode.php(32): OAuth2\ResponseType\AuthorizationCode->createAuthorizationCode('testclient', NULL, NULL, NULL) #3 /home/bas/development/codefined.com/oauth/www/oauth2-server-php/src/OAuth2/Controller/AuthorizeController.php(94): OAuth2\ResponseType\AuthorizationCode->getAuthorizeResponse(Array, NULL) #4 /home/bas/development in /home/bas/development/codefined.com/oauth/www/oauth2-server-php/src/OAuth2/Storage/Pdo.php on line 181
The text was updated successfully, but these errors were encountered: