Databases
StackOverflow2013
Postsdbo
POReading x-access-Level header for Twitter REST API using omniauth-twitter / twitter Gem
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReading x-access-Level header for Twitter REST API using omniauth-twitter / twitter Gem
    primarykey
    data
    text
    <p>I'm using Omniauth to authenticate users with Twitter through OAuth (using <code>omniauth-twitter</code> gem). I plan to allow normal users to login with just 'read' permissions, and only authorise 'read-write' permissions if/when they decide to create things within the site.</p> <p>In my <code>Identity</code> model I'm analysing the <code>AuthHash</code> omniauth passes to the create_with_omniauth action, and I'm making separate logic for each provider type, so that I can look deeper into the returned hash schema if necessary.</p> <p>If I <code>raise auth.to_yaml</code> to output the structure, I see the 'x-access-level' header that I'd like to read, but I don't know how to look into the <code>response: Net::HTTPOK</code> object in order to get to the next level of the structure.</p> <p>This is the auth structure, <em>cutting out some of the unnecessary details</em></p> <pre><code>--- !ruby/hash:OmniAuth::AuthHash provider: twitter ... extra: !ruby/hash:Hashie::Mash ... access_token: !ruby/object:OAuth::AccessToken ... response: !ruby/object:Net::HTTPOK http_version: '1.1' code: '200' message: OK header: x-access-level: - read-write x-ratelimit-limit: - '350' x-ratelimit-remaining: - '348' x-ratelimit-reset: - '1330798604' </code></pre> <p>So far I can get to the response with <code>auth["extra"]["access_token"].response</code> but putting <code>.header</code> at the end returns the same response structure, and <code>["header"]</code> is empty when I raise it.</p> <p>I'm ok with using the Twitter gem if necessary to do a <code>verify_credentials</code> call inside the Identity model (since Twitter adds the x-access-level header to every response, but even with this approach I wouldn't know how to read the returned headers to read the x-access-level header.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdsample
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWhich way did you go in the end?
      singulars
      1. POReading x-access-Level header for Twitter REST API using omniauth-twitter / twitter Gem
      1. USThomas Klemm
    2. COUnfortunately I haven't had much time to spend on my own projects since I asked, but the author of the omniauth-twitter gem did make some changes (might be in a branch on his github repo) to try and get it to work. IIRC I tried and couldn't get it to work immediately, but then I didn't have time to work on it.
      singulars
      1. POReading x-access-Level header for Twitter REST API using omniauth-twitter / twitter Gem
      1. USdsample
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload