Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You're on the right track. Google's OP Identifier (which is what you must enter to do a Google login) is <a href="https://www.google.com/accounts/o8/id" rel="nofollow noreferrer">https://www.google.com/accounts/o8/id</a></p> <ul> <li><code>realm</code> is the URL to your home page</li> <li><code>thisPageUrl</code> is the URL that the Provider should redirect the user back to after the user logs into the Provider.</li> <li>'requestUrl' is the full URL of the current incoming request, including query string. It may be carrying an OpenID response.</li> </ul> <p>So the only URL you likely need to change is the <code>realm</code> variable.</p> <p>Since you say you're getting a response back from Google already with a bunch of stuff in the query string, the code that processes that response should kick in. You may want to customize the actual login code (the part that sets Session variables) to whatever you site needs.</p> <p>The classic ASP COM server in DotNetOpenAuth v3.4.5 does actually enable you to get a Google user's email address. You do need to modify the sample slightly:</p> <pre><code>-redirectUrl = dnoi.CreateRequestWithSimpleRegistration(Request.Form("openid_identifier"), realm, thisPageUrl, "nickname,email", "fullname") +redirectUrl = dnoi.CreateRequestWithSimpleRegistration(Request.Form("openid_identifier"), realm, thisPageUrl, "", "email") </code></pre> <p>This should do it. If not, it may be that Google requires RP discovery to succeed. RP Discovery is a good thing to make work anyway. The directions to do it are at <a href="http://blog.nerdbank.net/2008/06/why-yahoo-says-your-openid-site.html" rel="nofollow noreferrer">http://blog.nerdbank.net/2008/06/why-yahoo-says-your-openid-site.html</a>. Note though that classic ASP wasn't the audience I had in mind when writing the post, so you may need to adapt some techniques a bit.</p>
    singulars
    1. This table or related slice is empty.
    1. POImplementing OpenID (DotNetOpenAuth) with Classic ASP
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndrew Arnott
    1. USAndrew Arnott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POImplementing OpenID (DotNetOpenAuth) with Classic ASP
      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
    1. COAndrew, thanks. I responded back to the Google Groups thread, but also thought I'd ask this... From what I've managed to gather, I won't be able to get an email address back in the "clientresponse". I understand they (Google) don't implement a particular feature of the openid framework, but could some alternative method be provided so I can found out the user's email address to create a stub account for them on my site?
      singulars
      1. PO
      1. USBrian
    2. COI've added to my answer to include the Google email solution.
      singulars
      1. PO
      1. USAndrew Arnott
 

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