blocks|key|4684453|text|我不知道这是不是正确的方法，但解决方案是这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4684454|def+index
++user+=+current_user
++user+%7C%7C=+User.find(doorkeeper_token[:resource_owner_id])+if+doorkeeper_token
++@habits+=+user.habits
end|code-block|syntax|javascript|4684455|您不能将其赋值给current_user，否则会将其设置为nil。|offset|length|style|CODE|4684456|entityMap^0|0|0|8|C|T|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I don't know if this is the right method or not, but a solution is to do:

<pre><code>def index
 user = current_user
 user ||= User.find(doorkeeper_token[:resource_owner_id]) if doorkeeper_token
 @habits = user.habits
end
</code></pre>

You can't assign to <code>current_user</code> or it will set it to <code>nil</code>.

blocks|key|178423|text|我会覆盖你的基础应用程序接口控制器中的current_user，类似于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178424|private

def+current_user
++@current_user+%7C%7C=+User.find(doorkeeper_token[:resource_owner_id])
end|code-block|syntax|javascript|178425|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I would override current_user in your base API controller, something like:

<pre><code>private

def current_user
 @current_user ||= User.find(doorkeeper_token[:resource_owner_id])
end
</code></pre>

blocks|key|4684534|text|来自Doorkeeper's+README的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4684535|经过身份验证的资源所有者|4684536|如果您希望根据当前资源所有者(即访问令牌所有者)返回数据，则可能需要在控制器中定义一个返回资源所有者实例的方法：|4684537|class+Api::V1::CredentialsController+<+Api::V1::ApiController
++before_action+:doorkeeper_authorize!
++respond_to++++:json

++#+GET+/me.json
++def+me
++++respond_with+current_resource_owner
++end

++private

++#+Find+the+user+that+owns+the+access+token
++def+current_resource_owner
++++User.find(doorkeeper_token.resource_owner_id)+if+doorkeeper_token
++end
end|code-block|syntax|javascript|4684538|在本例中，我们将返回访问令牌所有者的凭据(me.json)。|style|CODE|4684539|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/doorkeeper-gem/doorkeeper#authenticated-resource-owner^0|2|J|0|0|0|0|0|L|7|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|15|8|@$A|16|B|17|O|P]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

From <a href="https://github.com/doorkeeper-gem/doorkeeper#authenticated-resource-owner" rel="noreferrer">Doorkeeper's README</a> ...

<h3>Authenticated resource owner</h3>

If you want to return data based on the current resource owner, in other
words, the access token owner, you may want to define a method in your
controller that returns the resource owner instance:

<pre><code>class Api::V1::CredentialsController &lt; Api::V1::ApiController
 before_action :doorkeeper_authorize!
 respond_to :json

 # GET /me.json
 def me
 respond_with current_resource_owner
 end

 private

 # Find the user that owns the access token
 def current_resource_owner
 User.find(doorkeeper_token.resource_owner_id) if doorkeeper_token
 end
end
</code></pre>

In this example, we're returning the credentials (<code>me.json</code>) of the access
token owner.

blocks|key|4684582|text|我有一个API，需要允许通过Doorkeeper或Devise进行身份验证。下面的解决方案允许主应用程序使用与Oauth客户端相同的端点，并共享current_user方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4684583|before_action+:doorkeeper_authorize!,+unless:+:user_signed_in?

def+current_user
++@current_user+%7C%7C=+if+doorkeeper_token
++++++++++++++++++++++User.find(doorkeeper_token.resource_owner_id)
++++++++++++++++++++else
++++++++++++++++++++++warden.authenticate(scope:+:user)
++++++++++++++++++++end
end|code-block|syntax|javascript|4684584|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I have an API that needed to allow authentication via Doorkeeper OR Devise. The following solution allows the main application to use the same endpoints that Oauth clients would use and share the current_user method.

<pre><code>before_action :doorkeeper_authorize!, unless: :user_signed_in?

def current_user
 @current_user ||= if doorkeeper_token
 User.find(doorkeeper_token.resource_owner_id)
 else
 warden.authenticate(scope: :user)
 end
end
</code></pre>

I have a <a href="//github.com/wholcomb/smoke_tracker_rails" rel="noreferrer">rails app</a> that I am attempting to sync with an <a href="https://github.com/wholcomb/smoke_tracker" rel="noreferrer">android app</a>. I've successfully set up <a href="https://github.com/wholcomb/smoke_tracker/blob/add-syncadapter/src/com/synaptian/smoketracker/habits/authenticator/AuthenticatorActivity.java" rel="noreferrer">authentication</a> using <a href="https://github.com/applicake/doorkeeper" rel="noreferrer">Doorkeeper</a> as the server and <a href="http://oltu.apache.org" rel="noreferrer">Oltu</a> as the client.

My app tracks habits which exist as per-user lists. My index method in the habits controller is:

<pre><code>def index
 @habits = current_user.habits
end
</code></pre>

When authenticating via Devise this method works, when using Doorkeeper <code>current_user</code> is <code>nil</code>.

How to access current_user from a Doorkeeper authenticated session

身份验证

服务器

我有一个正在尝试与同步的。我已经成功地设置了，使用作为服务器，作为客户端。我的应用程序跟踪存在于每个用户列表中的习惯。我在习惯控制器中的索引方法是：def index  @habits = current_user.habitsend通过Devise进行身份验证时，此方法有效，使用Doorkeeper时，current...

问如何从Doorkeeper身份验证会话访问current_user
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从Doorkeeper身份验证会话访问current_userEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从Doorkeeper身份验证会话访问current_user
EN