openid-selector - Project Hosting on Google Code

Last 30 days Nov 28, 2009 issue 13 (Is facebook supposed to be supported?) reported by dan94501 - I see that there is an image for facebook in the image directory. Yet it doesn't appear in the javascript file. Is it intended to support Facebook? I read that facebook is now embracing OpenID, but it's not clear how or if that's really in place or not. It might be nice to at least note what the status of facebook integration is -- I'd like to offer that in my login panel if possible. I see that there is an image for facebook in the image directory. Yet it doesn't appear in the javascript file. Is it intended to support Facebook? I read that facebook is now embracing OpenID, but it's not clear how or if that's really in place or not. It might be nice to at least note what the status of facebook integration is -- I'd like to offer that in my login panel if possible. Nov 26, 2009 r25 ([No log message]) committed by david.j.boden - [No log message] [No log message] Nov 26, 2009 r24 ([No log message]) committed by david.j.boden - [No log message] [No log message] Earlier this year Aug 06, 2009 issue 11 (clicking a new openid logges you into the old one) commented on by jonsagara - You can also make the following modification to setOpenIdUrl: Change this: hidden.value = url; To this: hidden.val(url); You can also make the following modification to setOpenIdUrl: Change this: hidden.value = url; To this: hidden.val(url); Jul 07, 2009 issue 12 (If basic "openid" is open when user picks google or Yahoo, "...) reported by ptarjan - Changing the line : hidden.value = url; to : hidden.val(url); fixes the issue. Changing the line : hidden.value = url; to : hidden.val(url); fixes the issue. Jul 06, 2009 issue 11 (clicking a new openid logges you into the old one) reported by ptarjan - Changing the else condition of the signin function to : } else { openid.provider_url = provider['url']; if (! onload) { $('#openid_form').submit(); } } Fixes it for me. The problem is that the submit function overwrites the hidden url field with your cookie's provider instead of the one the user clicked on. Changing the else condition of the signin function to : } else { openid.provider_url = provider['url']; if (! onload) { $('#openid_form').submit(); } } Fixes it for me. The problem is that the submit function overwrites the hidden url field with your cookie's provider instead of the one the user clicked on. Jun 29, 2009 issue 9 (Invalid identifier when clicking on the wrong provider) commented on by jonathanparkeremail - Thanks. I will look at updating when I get some spare time. Thanks. I will look at updating when I get some spare time. Jun 29, 2009 issue 9 (Invalid identifier when clicking on the wrong provider) commented on by kweejee - The latest source code that you can check out with SVN fixes this. The featured download version should probably be updated. The latest source code that you can check out with SVN fixes this. The featured download version should probably be updated. Jun 29, 2009 issue 10 (http://yahoo.com/ doesn't work but http://me.yahoo.com/ does) reported by kweejee - Logging in through yahoo was not working. I'm using the Zend Framework so this is probably a bug in that code, but I only had to change the address in the selector to fix it. Using Yahoo's URL of http://yahoo.com/ was giving me an error about having an invalid OpenId. I changed it to http://me.yahoo.com/ and it works as expected. Hopefully this will be useful for anyone else trying to use Zend and openid-selector. Logging in through yahoo was not working. I'm using the Zend Framework so this is probably a bug in that code, but I only had to change the address in the selector to fix it. Using Yahoo's URL of http://yahoo.com/ was giving me an error about having an invalid OpenId. I changed it to http://me.yahoo.com/ and it works as expected. Hopefully this will be useful for anyone else trying to use Zend and openid-selector. May 11, 2009 issue 9 (Invalid identifier when clicking on the wrong provider) reported by jonathanparkeremail - What steps will reproduce the problem? 1. Go to http://www.mindmelder.org/Users/Login 2. Click on OpenId 3. Click on Yahoo! 4. Invalid identifier is shown. What is the expected output? Redirect to Yahoo! login. What version of the product are you using? 1.0 I think this may has something to do with cookies. What steps will reproduce the problem? 1. Go to http://www.mindmelder.org/Users/Login 2. Click on OpenId 3. Click on Yahoo! 4. Invalid identifier is shown. What is the expected output? Redirect to Yahoo! login. What version of the product are you using? 1.0 I think this may has something to do with cookies. May 05, 2009 issue 8 (Use openid_identifier as the form name and test interaction ...) reported by david.j.boden - Test whether Verisign's Seatbelt Firefox plugin currently interacts well with the selector. At the moment, I don't see that the Verisign PIP URL will be put into openid_identifier successfully. There will be a range of browser plugins supporting OpenID released over the next year or so. We should make sure they work well with the selector. The 2.0 spec says: http://openid.net/specs/openid-authentication-2_0.html The form field's "name" attribute SHOULD have the value "openid_identifier", so that User-Agents can automatically determine that this is an OpenID form. Browser extensions or other software that support OpenID Authentication may not detect a Relying Party's support if this attribute is not set appropriately. Test whether Verisign's Seatbelt Firefox plugin currently interacts well with the selector. At the moment, I don't see that the Verisign PIP URL will be put into openid_identifier successfully. There will be a range of browser plugins supporting OpenID released over the next year or so. We should make sure they work well with the selector. The 2.0 spec says: http://openid.net/specs/openid-authentication-2_0.html The form field's "name" attribute SHOULD have the value "openid_identifier", so that User-Agents can automatically determine that this is an OpenID form. Browser extensions or other software that support OpenID Authentication may not detect a Relying Party's support if this attribute is not set appropriately. May 05, 2009 StayingLoggedInBetweenPages (Storing details in a cookie to maintain login while navigati...) Wiki page added by david.j.boden May 04, 2009 r22 (Update mime types.) committed by david.j.boden - Update mime types. Update mime types. May 04, 2009 r21 (Issue5 Support AJAX openid_immediate mode. Also implementing...) committed by david.j.boden - Issue5 Support AJAX openid_immediate mode. Also implementing http://code.google.com/p/openid- selector/wiki/JavascriptOpenIDClient Issue5 Support AJAX openid_immediate mode. Also implementing http://code.google.com/p/openid- selector/wiki/JavascriptOpenIDClient May 02, 2009 JavascriptOpenIDClient (Proposal for a separate Javascript file which will perform a...) Wiki page edited by david.j.boden May 01, 2009 JavascriptOpenIDClient (Proposal for a separate Javascript file which will perform a...) Wiki page edited by david.j.boden May 01, 2009 JavascriptOpenIDClient (Proposal for a separate Javascript file which will perform a...) Wiki page added by david.j.boden Apr 29, 2009 r17 (More width for Verisign top level button.) committed by david.j.boden - More width for Verisign top level button. More width for Verisign top level button. Apr 29, 2009 r16 (Bumped VeriSign up to a top level provider by default. VeriS...) committed by david.j.boden - Bumped VeriSign up to a top level provider by default. VeriSign are currently offering two-factor One Time Password authentication for free using their PIP site and therefore qualify as an important player. Bumped VeriSign up to a top level provider by default. VeriSign are currently offering two-factor One Time Password authentication for free using their PIP site and therefore qualify as an important player. Apr 29, 2009 issue 2 (Previous Url requested) Status changed by david.j.boden - Status: Fixed Status: Fixed Apr 29, 2009 r15 (Issue2 Previous Url requested - removed the confusion where ...) committed by david.j.boden - Issue2 Previous Url requested - removed the confusion where the setOpenIdUrl method was being called multiple times. Issue2 Previous Url requested - removed the confusion where the setOpenIdUrl method was being called multiple times. Apr 29, 2009 issue 7 (Add a client javascript-only demo mode to prevent form submi...) Status changed by david.j.boden - Status: Fixed Status: Fixed Apr 29, 2009 r14 (Issue7 Add a client javascript-only demo mode to prevent for...) committed by david.j.boden - Issue7 Add a client javascript-only demo mode to prevent form submission when testing Issue7 Add a client javascript-only demo mode to prevent form submission when testing Apr 29, 2009 issue 7 (Add a client javascript-only demo mode to prevent form submi...) reported by david.j.boden - Adding a setDemoMode(false) method will allow the client javascript code to be more easily tested without having a server. It will be clear to see which OpenID URL is going to be transmitted to the server. Adding a setDemoMode(false) method will allow the client javascript code to be more easily tested without having a server. It will be clear to see which OpenID URL is going to be transmitted to the server. Apr 29, 2009 issue 2 (Previous Url requested) Labels changed by david.j.boden - Labels: Priority-Critical −Priority-Medium Labels: Priority-Critical −Priority-Medium Apr 29, 2009 issue 5 (Support AJAX openid_immediate mode) Labels changed by david.j.boden - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Apr 29, 2009 issue 6 (Degrade better when Javascript is not available) reported by david.j.boden - The interface already degrades pretty well when Javascript is not available. The user simply gets a single text box that they can use to submit their entire OpenID URL. This can be improved upon simply for providers like Google and Yahoo where the users just need to click on a button. We can provide a simple image that is just an <a/> link to the server with ?provider=google or ?provider=yahoo. These links would be part of a <div/> that is removed by Javascript before the page is rendered. If there's no Javascript then there's nothing to remove the <div/> and links will show up. The providers that require a username are more difficult. These will have to be removed. The interface already degrades pretty well when Javascript is not available. The user simply gets a single text box that they can use to submit their entire OpenID URL. This can be improved upon simply for providers like Google and Yahoo where the users just need to click on a button. We can provide a simple image that is just an <a/> link to the server with ?provider=google or ?provider=yahoo. These links would be part of a <div/> that is removed by Javascript before the page is rendered. If there's no Javascript then there's nothing to remove the <div/> and links will show up. The providers that require a username are more difficult. These will have to be removed. Apr 29, 2009 r13 (Ignore .project file created by Eclipse.) committed by david.j.boden - Ignore .project file created by Eclipse. Ignore .project file created by Eclipse. Apr 29, 2009 issue 5 (Support AJAX openid_immediate mode) reported by david.j.boden - In addition to supporting form submission which will result in a browser redirect, the client selector should also support an AJAX workflow. In this workflow, the user clicks on a provider and when AJAX is enabled a quick Javascript call is made to the server. The server makes an openid_immediate mode call to the provider to see if the user can be authenticated (because they logged in recently) without bothering to redirect the browser to the provider's page at all. If the user can be authenticated in this way, the server updates the user's session and replies to the client selector to say that the user is now successfully logged in. If the user can't be authorised, the AJAX method should be notified and the client selector can decide (based on whether a developer's method replies with true or false) whether to just prompt the user with an error message, ask for confirmation to redirect the browser or just go ahead and redirect the browser (default behaviour). This feature will degrade nicely when Javascript is not available. It'll just not be available. The feature will be disabled by default. In the best case scenario, this feature allows the user to be authenticated in a split-second without the browser page having to be refreshed at all. We'll have to take care with providers like Google where you don't provide your username up front. The user may need a way of saying "log me into Google, but not as the user that I'm currently logged in with". This is a pretty rare use case, though. In addition to supporting form submission which will result in a browser redirect, the client selector should also support an AJAX workflow. In this workflow, the user clicks on a provider and when AJAX is enabled a quick Javascript call is made to the server. The server makes an openid_immediate mode call to the provider to see if the user can be authenticated (because they logged in recently) without bothering to redirect the browser to the provider's page at all. If the user can be authenticated in this way, the server updates the user's session and replies to the client selector to say that the user is now successfully logged in. If the user can't be authorised, the AJAX method should be notified and the client selector can decide (based on whether a developer's method replies with true or false) whether to just prompt the user with an error message, ask for confirmation to redirect the browser or just go ahead and redirect the browser (default behaviour). This feature will degrade nicely when Javascript is not available. It'll just not be available. The feature will be disabled by default. In the best case scenario, this feature allows the user to be authenticated in a split-second without the browser page having to be refreshed at all. We'll have to take care with providers like Google where you don't provide your username up front. The user may need a way of saying "log me into Google, but not as the user that I'm currently logged in with". This is a pretty rare use case, though. Apr 29, 2009 issue 4 (Rewrite of openid-selector.) Status changed by david.j.boden - Closing this issue because your openid-realselector project is now mentioned on the front page of openid-selector. Status: Invalid Closing this issue because your openid-realselector project is now mentioned on the front page of openid-selector. Status: Invalid Apr 29, 2009 issue 3 (not working with Google - annoying warning with Yahoo) Status changed by david.j.boden - Closing as this isn't an issue with the client side selector. Status: WontFix Closing as this isn't an issue with the client side selector. Status: WontFix Apr 29, 2009 issue 1 (aol url wrong) changed by david.j.boden - Status: Fixed Owner: david.j.boden Status: Fixed Owner: david.j.boden Apr 29, 2009 r12 (Issue1 aol url wrong - Fixed) committed by david.j.boden - Issue1 aol url wrong - Fixed Issue1 aol url wrong - Fixed Apr 29, 2009 r11 ([No log message]) committed by david.j.boden - [No log message] [No log message] Apr 28, 2009 r10 ([No log message]) committed by david.j.boden - [No log message] [No log message] Apr 28, 2009 r9 ([No log message]) committed by david.j.boden - [No log message] [No log message] Apr 28, 2009 r8 (Set mime-type to text/javascript so that we can see the demo...) committed by david.j.boden - Set mime-type to text/javascript so that we can see the demo javascript served directly from the SVN server in Firefox. Set mime-type to text/javascript so that we can see the demo javascript served directly from the SVN server in Firefox. Apr 28, 2009 r7 (Set mime-type to image/... so that we can see the demo image...) committed by david.j.boden - Set mime-type to image/... so that we can see the demo images served directly from the SVN server in Firefox. Set mime-type to image/... so that we can see the demo images served directly from the SVN server in Firefox. Apr 28, 2009 r6 (Set mime-type to text/html so that we can see the demo serve...) committed by david.j.boden - Set mime-type to text/html so that we can see the demo served directly from the SVN server. Set mime-type to text/html so that we can see the demo served directly from the SVN server. Jan 17, 2009 issue 2 (Previous Url requested) commented on by Reflejo - I just rewrite this selector, now supports internacionalization and is smaller (js: 2.8k compressed, 4.7k full) Since i couldn't contact the author i made another project: http://code.google.com/p/openid-realselector/ I just rewrite this selector, now supports internacionalization and is smaller (js: 2.8k compressed, 4.7k full) Since i couldn't contact the author i made another project: http://code.google.com/p/openid-realselector/ Jan 17, 2009 issue 4 (Rewrite of openid-selector.) reported by Reflejo - I just rewrite this selector, now supports internacionalization and is smaller (js: 2.8k compressed, 4.7k full) Since i couldn't contact the author i made another project: http://code.google.com/p/openid-realselector/ I just rewrite this selector, now supports internacionalization and is smaller (js: 2.8k compressed, 4.7k full) Since i couldn't contact the author i made another project: http://code.google.com/p/openid-realselector/ Jan 16, 2009 issue 3 (not working with Google - annoying warning with Yahoo) reported by miccorne - Hello, I installed openid-selector 1.0 (I really like the simplicity and scalability of the interface) and php-openid 2.1.2 on my site. I ran some tests. The auth works fine with my myopenid account. But I have 2 issues: - Google returns "The server could not process your request." I cannot even get to the login page and get a chance to use my Google account. What should be done so that it works with Google? - That works fine with my Yahoo account but there is an annoying message in the Yahoo page that says "warning! This web site has not confirmed its identity ...". Should I do something special with Yahoo so my site is not flagged that way? I realize those issues are not due to openid-selector since I get the same problem when I use php-openid/consumer/index.php directly. But I am asking you guys anyway as you may have run into this as well. Many thanks, MC Hello, I installed openid-selector 1.0 (I really like the simplicity and scalability of the interface) and php-openid 2.1.2 on my site. I ran some tests. The auth works fine with my myopenid account. But I have 2 issues: - Google returns "The server could not process your request." I cannot even get to the login page and get a chance to use my Google account. What should be done so that it works with Google? - That works fine with my Yahoo account but there is an annoying message in the Yahoo page that says "warning! This web site has not confirmed its identity ...". Should I do something special with Yahoo so my site is not flagged that way? I realize those issues are not due to openid-selector since I get the same problem when I use php-openid/consumer/index.php directly. But I am asking you guys anyway as you may have run into this as well. Many thanks, MC Jan 12, 2009 issue 2 (Previous Url requested) commented on by mjezorek - I will have to find it again the only change I made to the html that I remember is the addition of the <div id="openid_error"></div> which is only used in one case and thats when someone uses the OpenID large image and does not enter a value so it just puts a simple message in it saying please enter your open id. I will look for the sample I was using I just recently reformatted my PC to put windows 7 on it for some testing I will have to find it again the only change I made to the html that I remember is the addition of the <div id="openid_error"></div> which is only used in one case and thats when someone uses the OpenID large image and does not enter a value so it just puts a simple message in it saying please enter your open id. I will look for the sample I was using I just recently reformatted my PC to put windows 7 on it for some testing Jan 10, 2009 issue 2 (Previous Url requested) commented on by tracy.grand - Hi mjezorek, That last version seems to be working. I didn't have to change the HTML, other than to reference the new file name. Please upload your sample HTML if there are other changes I should make. Tracy Hi mjezorek, That last version seems to be working. I didn't have to change the HTML, other than to reference the new file name. Please upload your sample HTML if there are other changes I should make. Tracy Jan 08, 2009 issue 2 (Previous Url requested) commented on by mjezorek - Fixed two small bugs in the previous upload. Also there is a <div id="openid_error"></div> you can add to your html to get some basic error handling Fixed two small bugs in the previous upload. Also there is a <div id="openid_error"></div> you can add to your html to get some basic error handling Jan 08, 2009 issue 2 (Previous Url requested) commented on by mjezorek - Not sure but I ended up rewriting it slightly. You can try this version however it will need a couple small mods in your html page. I opened up the settings to overrides so you can change the providers shown if you want or anything thats in the settings. for example you can change to only use Google as a large image if you want $(document.ready(function() { $.openid({ // your settings here img_path: '/images/', input_id: 'openid_identifier', providers_large: { google: { name: 'Google', url: 'http://ww.google.com/accounts/o8/id' } } }); }); I have not tested in all browsers but here is the begining of the rewrite. I may end up setting up a new project if the owner does not show up soon. Let me know if this does not work for you Not sure but I ended up rewriting it slightly. You can try this version however it will need a couple small mods in your html page. I opened up the settings to overrides so you can change the providers shown if you want or anything thats in the settings. for example you can change to only use Google as a large image if you want $(document.ready(function() { $.openid({ // your settings here img_path: '/images/', input_id: 'openid_identifier', providers_large: { google: { name: 'Google', url: 'http://ww.google.com/accounts/o8/id' } } }); }); I have not tested in all browsers but here is the begining of the rewrite. I may end up setting up a new project if the owner does not show up soon. Let me know if this does not work for you Jan 07, 2009 issue 2 (Previous Url requested) commented on by tracy.grand - where is the author andyjm????!!! where is the author andyjm????!!! Jan 06, 2009 issue 2 (Previous Url requested) commented on by mjezorek - Gah I found another bug in that so that fix does not fix everything Gah I found another bug in that so that fix does not fix everything Jan 06, 2009 issue 2 (Previous Url requested) commented on by mjezorek - I am not the author but try this .js file I made a change that seems to work for me. Brief fix details so you can modify your own if you like. In the signin function signin: function(box_id, onload) { var provider = providers[box_id]; if(!provider) { return; } this.highlight(box_id); this.setCookie(box_id); this.provider_url = provider['url']; // FIX IS HERE ADD THIS LINE if(provider['label']) { this.useInputBox(provider); } else { this.setOpenIdUrl(provider['url']); if(!onload) { $('#openid_form').submit(); } } }, } I am not the author but try this .js file I made a change that seems to work for me. Brief fix details so you can modify your own if you like. In the signin function signin: function(box_id, onload) { var provider = providers[box_id]; if(!provider) { return; } this.highlight(box_id); this.setCookie(box_id); this.provider_url = provider['url']; // FIX IS HERE ADD THIS LINE if(provider['label']) { this.useInputBox(provider); } else { this.setOpenIdUrl(provider['url']); if(!onload) { $('#openid_form').submit(); } } }, } Jan 05, 2009 issue 2 (Previous Url requested) commented on by tracy.grand - I'm having the same problem. I did some debugging and it changes the hidden openid_identifier value twice when you sign in to a service. The first time is correct and happens during the signin in routine. The second time it happens it uses the prior value and that happens during the submit routine. Please fix this, as we would like to use the code! I'm having the same problem. I did some debugging and it changes the hidden openid_identifier value twice when you sign in to a service. The first time is correct and happens during the signin in routine. The second time it happens it uses the prior value and that happens during the submit routine. Please fix this, as we would like to use the code!

issue 5 (Support AJAX openid_immediate mode) reported by david.j.boden - In addition to supporting form submission which will result in a browser redirect, the client selector should also support an AJAX workflow. In this workflow, the user clicks on a provider and when AJAX is enabled a quick Javascript call is made to the server. The server makes an openid_immediate mode call to the provider to see if the user can be authenticated (because they logged in recently) without bothering to redirect the browser to the provider's page at all. If the user can be authenticated in this way, the server updates the user's session and replies to the client selector to say that the user is now successfully logged in. If the user can't be authorised, the AJAX method should be notified and the client selector can decide (based on whether a developer's method replies with true or false) whether to just prompt the user with an error message, ask for confirmation to redirect the browser or just go ahead and redirect the browser (default behaviour). This feature will degrade nicely when Javascript is not available. It'll just not be available. The feature will be disabled by default. In the best case scenario, this feature allows the user to be authenticated in a split-second without the browser page having to be refreshed at all. We'll have to take care with providers like Google where you don't provide your username up front. The user may need a way of saying "log me into Google, but not as the user that I'm currently logged in with". This is a pretty rare use case, though.

In addition to supporting form submission which will result in a browser redirect, the client selector should also support an AJAX workflow. In this workflow, the user clicks on a provider and when AJAX is enabled a quick Javascript call is made to the server. The server makes an openid_immediate mode call to the provider to see if the user can be authenticated (because they logged in recently) without bothering to redirect the browser to the provider's page at all. If the user can be authenticated in this way, the server updates the user's session and replies to the client selector to say that the user is now successfully logged in. If the user can't be authorised, the AJAX method should be notified and the client selector can decide (based on whether a developer's method replies with true or false) whether to just prompt the user with an error message, ask for confirmation to redirect the browser or just go ahead and redirect the browser (default behaviour). This feature will degrade nicely when Javascript is not available. It'll just not be available. The feature will be disabled by default. In the best case scenario, this feature allows the user to be authenticated in a split-second without the browser page having to be refreshed at all. We'll have to take care with providers like Google where you don't provide your username up front. The user may need a way of saying "log me into Google, but not as the user that I'm currently logged in with". This is a pretty rare use case, though.

Last 30 days

Earlier this year