Undefined method `openid_request' using custom access grant class. about doorkeeper-openid_connect HOT 4 CLOSED

@phlegx thanks for the report! I'm not sure if we already have access to Doorkeeper's configuration when that prepend call happens. 🤔

But the has_one association is defined at

Let me know if that works and is an acceptable solution, and I'll add a note to the README similar to https://doorkeeper.gitbook.io/guides/configuration/models. We could also support include in addition to prepend to make it look more consistent.

from doorkeeper-openid_connect.

So, I should put prepend ::Doorkeeper::OpenidConnect::AccessGrant in my AccessGrant model instead of the has_one relation workaround?

from doorkeeper-openid_connect.

@phlegx yes, that should pull in the has_one definition and any other future changes (prepend acts similarly to include). Let me know if that works for you!

I was also curious now if we could just monkey-patch Doorkeeper::Orm::ActiveRecord::Mixins::AccessGrant rather than Doorkeeper::Orm::ActiveRecord::AccessGrant, but I couldn't find a way to inject code into the existing included block there (getting a ActiveSupport::Concern::MultipleIncludedBlocks error).

from doorkeeper-openid_connect.

Just adding a note here that I needed to specify:

    has_one :openid_request,
            class_name: 'Doorkeeper::OpenidConnect::Request',
            inverse_of: :access_grant,
            dependent:  :delete

and include foreign_key: 'access_grant_id' due to my team customizing the AccessGrant table_name. Without the foreign_key constraint specified, I received the following MySQL error:

Mysql2::Error: Unknown column 'oauth_openid_requests.{custom_table_name}_id' in 'where clause': SELECT  `oauth_openid_requests`.* FROM `oauth_openid_requests` WHERE `oauth_openid_requests`.`{custom_table_name}_id` = X LIMIT 1

The schema at this point had already been using access_grant_id as the column name. It may be useful to add this to the Doorkeeper custom model docs.

from doorkeeper-openid_connect.