Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you are using <a href="https://github.com/zquestz/omniauth-google-oauth2" rel="nofollow">omniauth-google-oauth2</a>, you can accomplish domain restrictions using by providing a value for <code>hd</code> option during initialization.</p> <pre><code>Rails.application.config.middleware.use OmniAuth::Builder do provider :google_oauth2, ENV['GOOGLE_CLIENT_ID'], ENV['GOOGLE_CLIENT_SECRET'], { scope: 'email, profile', hd: 'mycompany.com' } end </code></pre> <p>It's also possible to handle this in your controller which is handling the callback. You can deny users depending on values provided in <a href="https://github.com/zquestz/omniauth-google-oauth2#auth-hash" rel="nofollow"><code>request.env["omniauth.auth"]</code></a>.</p> <pre><code>class OmniauthCallbacksController &lt; Devise::OmniauthCallbacksController def google_oauth2 auth_details = request.env["omniauth.auth"] if auth_details.info['email'].split("@")[1] == "yourdomain.com" # do all the bits that come naturally in the callback controller user = User.from_omniauth(request.env["omniauth.auth"]) if user.persisted? flash.notice = "Signed in Through Google!" sign_in_and_redirect user else session["devise.user_attributes"] = user.attributes flash.notice = "You are almost Done! Please provide a password to finish setting up your account" redirect_to new_user_registration_url end else # This is where you turn away the poor souls who do not match your domain render :text =&gt; "We're sorry, at this time we do not allow access to our app." end end end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIn Rails, is it possible to limit who can log in with google using the api?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlper Kokmen
    1. UStrh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIn Rails, is it possible to limit who can log in with google using the api?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi, Thank you very much for explanation! one question, why do you write [1] in .split("@")[1] ?
      singulars
      1. PO
      1. USNaomi K
    2. COsplit returns an array of items. In this case you're splitting on the @ sign so the two items left in the array are the portion before the @ sign and the domain after. So the [1] is denoting the second item in the array.
      singulars
      1. PO
      1. UStrh
    3. COHello, I am coming back to this question, sorry. but where did you get auth_details.info from? is this something omniauth already has? I ask because it doesnt seem to work
      singulars
      1. PO
      1. USNaomi K
 

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