summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Fixed minor issue that Ouroboros17 brought to my attention: 'Server.php give ↵Lilli2010-04-281-1/+1
|/ | | | me a notice error at line 1471 because ->code can be undefined. An isset test can correct the problem ;)'
* Removed/changed references to openidenabled.com. At this time, not every ↵2.2.0Lilli2010-03-166-27/+9
| | | | reference has been updated.
* Added the following patch from the trac.openidenabled.com bug tracker:Lilli2010-02-167-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | | http://trac.openidenabled.com/trac/ticket/338 (http://trac.openidenabled.com/trac/attachment/ticket/338/openid-php5.3.diff) Patch makes php-openid library compatible with PHP 5.3, and included changes to many files. Original Message: Reported by: http://paulisageek.com/ Opened 6 months ago Last modified 2 months ago php openid library doesn't seem to work with php 5.3 "I get many PHP warnings and then the error condition on the Consumer. Deprecated: Assigning the return value of new by reference is deprecated in *path*/Auth/OpenID/Consumer.php on line 271 Deprecated: Assigning the return value of new by reference is deprecated in *path*/Auth/OpenID/Consumer.php on line 273 Warning: Parameter 1 to filter_MatchesAnyOpenIDType() expected to be a reference, value given in *path*/Auth/Yadis/XRDS.php on line 431 Warning: Parameter 2 to Auth_OpenID_GenericConsumer::_completeInvalid() expected to be a reference, value given in *path*/Auth/OpenID/Consumer.php on line 669 " It should be noted that 3 hunks across 7 files failed, and I applied most of them manually. 7 files were patched.
* Added the following patch from the trac.openidenabled.com bug tracker:Lilli2010-02-1635-290/+233
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://trac.openidenabled.com/trac/ticket/337 (http://trac.openidenabled.com/trac/attachment/ticket/337/php-openid-php5.3.patch) Patch makes php-openid library compatible with PHP 5.3, and included changes to many files. Original Message: Reported by: http://bfarber.myopenid.com/ Opened 7 months ago Last modified 2 months ago PHP OpenID libraries do not work on PHP 5.3 "In my own application the script simply stops working at function Auth_OpenID_setNoMathSupport() { if (!defined('Auth_OpenID_NO_MATH_SUPPORT')) { define('Auth_OpenID_NO_MATH_SUPPORT', true); } } (Namespace issue perhaps?) I downloaded the latest 2.1.3 libraries available from the site here and set them up on my local server. Using PHP 5.2.9 they work fine (with some notices) however using PHP 5.3 they don't work at all. I just get this one a white screen Deprecated: Assigning the return value of new by reference is deprecated in C:\wamp\www\openid\php-openid-2.1.3\examples\consumer\common.php on line 72 Deprecated: Assigning the return value of new by reference is deprecated in C:\wamp\www\openid\php-openid-2.1.3\Auth\OpenID\Consumer.php on line 271 Deprecated: Assigning the return value of new by reference is deprecated in C:\wamp\www\openid\php-openid-2.1.3\Auth\OpenID\Consumer.php on line 273" It should be noted that 34 hunks across about 22 files failed, and I applied most of them manually. 37 files were patched.
* Added Google's add-on found at ↵Lilli2010-02-161-0/+0
| | | | | | | | | http://php-openid-apps-discovery.googlecode.com/files/php-openid-apps-discover-1.0.1.tar.gz to the contrib/google directory. Project Home: http://code.google.com/p/php-openid-apps-discovery/ "Add-on to JanRain's php-openid library that enables the use of Google Apps host domains as an IDP."
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-121-0/+20
| | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20090928/2d616914/attachment.bin Original Message: anthony.lenton at canonical.com anthony.lenton at canonical.com Mon Sep 28 11:30:12 PDT 2009 darcs patch: cURL verify host "With this patch, if you define Auth_Openid_VERIFY_HOST cURL will enable host verification on ssl connections, for added security." This patch was in the form of a Darcs patch, not a normal patch. So solve this, I applied it to the Darcs repository found on openidenabled, then created a new diff file between the original Darcs repo and the new one (with the patch applied) so that I could apply it to this git repo. All hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-122-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20090206/f0d91666/attachment-0001.bin Original Message: will at willnorris.com will at willnorris.com Fri Feb 6 14:56:12 PST 2009 darcs patch: Properly handle Yadis discovery failure "The library does not curently handle failures during Yadis discovery properly. Specifically, if Yadis discovery fails, and discovery WAS being done with an XRDS document, then non-Yadis discovery should be attempted. The use-case I'm dealing with right now that exposes this bug is when an XRDS document location is advertised (via HTTP response header or <meta /> HTML tag), but the document is not able to be retrieved for whatever reason. The library is failing in this case, instead of continuing to attempt non-Yadis discovery. This patch includes two changes: - change to Yadis/Yadis.php that properly detects if XRDS was used - change to OpenID/Discovery.php that prevents discovery from halting in the above example" This patch was in the form of a Darcs patch, not a normal patch. So solve this, I applied it to the Darcs repository found on openidenabled, then created a new diff file between the original Darcs repo and the new one (with the patch applied) so that I could apply it to this git repo. All hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-121-1/+1
| | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20090113/8ed067b3/attachment.bin Original Message: will at willnorris.com will at willnorris.com Sun Jan 4 11:27:26 PST 2009 darcs patch: I'm not entirely sure which versions of PHP are having... "I've had a number of users report that $this->store is incorrectly evaluating to false, thereby preventing associations from being used. I've been unable to reproduce this myself, but the change is minor enough." This patch was in the form of a Darcs patch, not a normal patch. So solve this, I applied it to the Darcs repository found on openidenabled, then created a new diff file between the original Darcs repo and the new one (with the patch applied) so that I could apply it to this git repo. All hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-123-4/+32
| | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20090109/7e344691/attachment-0001.bin Original Message: ketmar at ketmar.no-ip.org ketmar at ketmar.no-ip.org Fri Jan 9 07:51:35 PST 2009 darcs patch: fix for incomplete URIs in "location" http field (for ... "* fix for incomplete URIs in "location" http field (for technorati and maybe others)" This patch was in the form of a Darcs patch, not a normal patch. So solve this, I applied it to the Darcs repository found on openidenabled, then created a new diff file between the original Darcs repo and the new one (with the patch applied) so that I could apply it to this git repo. Hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-122-3/+3
| | | | | | | | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20090101/217f2590/attachment.bin Original Message: dev-list-openidenabled at thequod.de dev-list-openidenabled at thequod.de Thu Jan 1 18:14:12 PST 2009 darcs patch: php-openid-urldecode-urlparamkey "This patch also decodes the key of URL params, which is required for param names like 'action[foo]' when the browser sends those urlencoded (Konqueror 4.2 does so). I would like to propose using rawurldecode instead of urldecode, too, but that causes the tests to fail and may be against the OpenID spec (the difference is only that "+" gets decoded with urldecode() but not with rawurldecode IIRC)" This patch was in the form of a Darcs patch, not a normal patch. So solve this, I applied it to the Darcs repository found on openidenabled, then created a new diff file between the original Darcs repo and the new one (with the patch applied) so that I could apply it to this git repo. All hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-122-3/+39
| | | | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20080821/1eded806/attachment-0001.bin Original Message: will at willnorris.com Thu Aug 21 18:43:28 PDT 2008 darcs patch: seperate provider and consumer xrds types "Currently, the five OpenID Provider service types (OpenID 1.0 - 1.2, and the two for OpenID 2.0) are combined with the one OpenID Consumer service type (return_to). This causes a potential false positive when performing discovery on an endpoint. If a php-openid consumer performs discovery on another consumer which has a published return_to service type, php-openid will think it is a valid OpenID Server service type and send an authentication request to the URI. Similarly, when checking the return_to URL of a consumer, if the consumer has any of the OpenID Server service types published, a php-openid server object will try to treat one of those URIs as a published return_to URL. This scenario is actually fairly common... many personal blogs serve as both an OpenID Server (for the blog owner) as well as an OpenID consumer (for people who comment on the blog)." This patch was in the form of a Darcs patch, not a normal patch. So solve this, I applied it to the Darcs repository found on openidenabled, then created a new diff file between the original Darcs repo and the new one (with the patch applied) so that I could apply it to this git repo. It should be noted that all 3 hunks for Discover.php and the 1st hunk for TrustRoot.php were applied successfully, but the second hunk for TrustRoot failed. It seems that all it was doing was removing trailing endlines from the file, so I think it should be ok.
* Added the following patch from the trac.openidenabled.com ticket #253:Lilli2010-02-101-3/+22
| | | | | | | | | | | | | | | | | | | http://trac.openidenabled.com/trac/attachment/ticket/253/detect.patch.txt Original Message: Opened 2 years ago Reported by: http://openid.jamus.com/ detect.php - Detect "corruption" of query string by mod_encoding "The mod_encoding module "corrupts" the query string by translating %xx in the query sring to the character representation. For example, for the URL http://foo.com?a=a%26b, the QUERY_STRING should be a=a%26b, but with mod_encoding enabled, QUERY_STRING is a=a&b. This corruption prevents the library from working correctly. Attached is a simple patch to detect.php to detect this. I hope to save somebody else time tracking this down. mod_encoding was enabled by my webhost (dreamhost.com) when I enabled web_dav for the domain." All hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-102-6/+475
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20080221/f087874e/attachment.obj Original Messages: Ryan Patterson cgamesplay at cgamesplay.com Thu Feb 21 10:57:56 PST 2008 OpenIDStore for PEAR::MDB2 "On Thu, Feb 21, 2008 at 10:24 AM, Thomas Harning <thomas.harning at trustbearer.com> wrote: > Shortening the URLs to 255 chars has some ugly problems since the spec states > that the max Server URL can technically be up to 2047 bytes (per OpenID 1.1-Appendix D) Ah, I glanced at the spec but didn't see anything. > One option for databases that can't have a key large enough is using a prefix-based key... > I know MySQL supports this, but I'm not so sure on others. This is what the current SQLStore implementation does. I've modified the patch to add specific SQL for mysql backends, but use MDB2's generic table creation for other stores. The test cases in the patch pass for MDB2 using MySQL, but I'd like to verify that it works with PostgreSQL. -- Regards, Ryan Patterson <mailto:cgamesplay at cgamesplay.com>" Thomas Harning thomas.harning at trustbearer.com Thu Feb 21 07:24:02 PST 2008 OpenIDStore for PEAR::MDB2 "Ryan Patterson wrote: > I've created an Auth_OpenID_OpenIDStore implementation that utilizes > PEAR::MDB2 instead of PEAR::DB, called Auth_OpenID_MDB2Store. The > advantages to this store are that it supports all database back ends > that PEAR::MDB2 supports, and does not require the user to know which > database back end is being used when instantiating the store. Because > of the complete database abstraction, the entire store is > approximately 350 lines shorter than the SQLStore family. > > As a note to users planning to test this store: the table schema is > incompatible with the other SQLStores. Specifically, the length of > server URLs has been shortened to 255 characters to allow cross-RDBMS > compatibility, and the field types have been changed to NOT NULL. You > may safely delete your associations and nonces tables with no > consequences. Shortening the URLs to 255 chars has some ugly problems since the spec states that the max Server URL can technically be up to 2047 bytes (per OpenID 1.1-Appendix D) One option for databases that can't have a key large enough is using a prefix-based key... I know MySQL supports this, but I'm not so sure on others. Another option would be to use a unique value as the primary key and use some ugly mechanics so that you can store a 20 byte sha1 in a non-unique index and the server URL not in an index. The basic select would be SELECT * FROM Sites WHERE URLHash = ? AND URL = ?; The URLHash would narrow it down to likely one, where URL would clobber potential collisions and keep the data around if needed... -- Thomas Harning @ TrustBearer Labs (http://www.trustbearer.com) Secure OpenID: https://openid.trustbearer.com/harningt 3201 Stellhorn Road 260-399-1656 Fort Wayne, IN 46815" OpenIDStore for PEAR::MDB2 Ryan Patterson cgamesplay at cgamesplay.com Thu Feb 21 07:19:02 PST 2008 "I've created an Auth_OpenID_OpenIDStore implementation that utilizes PEAR::MDB2 instead of PEAR::DB, called Auth_OpenID_MDB2Store. The advantages to this store are that it supports all database back ends that PEAR::MDB2 supports, and does not require the user to know which database back end is being used when instantiating the store. Because of the complete database abstraction, the entire store is approximately 350 lines shorter than the SQLStore family. As a note to users planning to test this store: the table schema is incompatible with the other SQLStores. Specifically, the length of server URLs has been shortened to 255 characters to allow cross-RDBMS compatibility, and the field types have been changed to NOT NULL. You may safely delete your associations and nonces tables with no consequences. A test case has been added that tests the MDB2 store with a MySQL backend. I would appreciate it if someone capable could modify the test case and test it using PostgreSQL, to ensure that the database abstraction I've used is correct. -- Regards, Ryan Patterson <mailto:cgamesplay at cgamesplay.com>" All of the patch's hunks were applied successfully.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-101-3/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20080117/5d35b90c/attachment.obj Original Message: artemy tregoubenko me at arty.name Thu Jan 17 01:58:39 PST 2008 php: raw bytestrings vs. mb_string.func_overload and strlen "Hello. After all, patch for unicode support in 'html parser' is quite small. It solves my problems for now. On 1/16/08, artemy tregoubenko <me at arty.name> wrote: > Hello again! > > Today I switched to php-openid 2.0.0 and some things began working. > However, I experienced more problems with multibyte strings. Now they > happen at stage of fetching and parsing html documents. > ParanoidFetcher was easy to fix, patch for it attached. Currently I'm > hacking into ParseHTML, and using regexes in php-unicode environment > is a pain! > > -- > arty ( http://arty.name ) > > -- arty ( http://arty.name )" It should be noted that hunks 1 and 4, out of the patch's 4, were applied successfully, I manually applied hunk 2, and hunk 3 could no longer be applied for the same reason as the previous patch: In both cases, the patches modified the same function, and the current function no longer contains the lines of code that the 3rd hunk is trying to modify. On that note, both patches are modifying the same lines of code in the same function. From what I can tell from the email messages, they are fixing different issues, but it should be confirmed that the fixes are both needed and will play nicely together.
* Added the following patch from the dev@openidenabled.com mailing list:Lilli2010-02-101-1/+12
| | | | | | | | | | | | | | | | | | | | | | http://lists.openidenabled.com/pipermail/dev/attachments/20070117/14e9fc7d/attachment.bin Original Message: dAniel hAhler dev-list-openidenabled at thequod.de Wed Jan 17 14:02:44 PST 2007 [PHP-openid] PCRE backtrack error in Auth_OpenID_Parse::parseLinkAttrs() / todo (patch) "Hi, I find that the Auth_OpenID_Parse::parseLinkAttrs() method is quite ineffective. It failed here (silently), because of a PREG_BACKTRACK_LIMIT_ERROR in preg_match() (introduced with PHP 5.2). The attached patch adds a TODO with an idea of a better/more efficient implementation and a dirty workaround, by disabling this limit. It seems like the parsing fails if the HTML to get parsed is > 100KB or something similar. The default backtrack limit is 100000. ..." It should be noted that hunks 1, 4, and 5 out of the patch's 5 were applied successfully, I manually applied hunk 2, and hunk 3 could no longer be applied.
* Added the changes to consumer and consumer test that were made to ↵Lilli2010-02-082-19/+44
| | | | openidenabled.com's repo after the repo was moved to git hub
* still use in_array, just require strict type checkingWill Norris2009-05-281-4/+2
| | | Signed-off-by: Will Norris <will@willnorris.com>
* [ few random cleanup changes ]Luke Shepard2009-05-286-9/+44
| | | | | | | | A few minor changes made over the past few months. This adds some additional logging, an extra helper function for error messages, and fixes a small bug with the association handler ... not to mention standardizing on "false" instead of "False". Signed-off-by: Will Norris <will@willnorris.com>
* [ remove closing ?> tag from all files ]Luke Shepard2009-05-2876-76/+31
| | | | | | | | | | | | Reviewed By: Will Norris Facebook has a policy to not have closing ?> tags at the bottom of PHP files. It can unintentionally introduce newlines which causes ridiculous bugs. This is recommended in the Zend style guide: http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html Signed-off-by: Will Norris <will@willnorris.com>
* Revert "[ remove closing ?> tag from all files ]"Luke Shepard2009-05-27101-111/+172
| | | | | | This reverts commit a2bdc5c6129ff11b1c1e29a207b1b80153ac6fb0. I'm going to stop playing in bce's fork, and start messing in my own. Sorry for the mess Brian :)
* Revert "[ correct errors in removing trailing ?> ]"Luke Shepard2009-05-278-84/+73
| | | | This reverts commit f963a700e4440074a5b86d382789e75795206482.
* [ correct errors in removing trailing ?> ]Luke Shepard2009-05-278-73/+84
| | | | | | | | In the last commit, I over-aggressively removed closing PHP tags. While I dislike the practice of using close tags within templates, it is how this library works, so let's put them back. Checked that all PHP compiles with "php -l".
* [ remove closing ?> tag from all files ]Luke Shepard2009-05-27101-172/+111
| | | | | | | | | | Reviewed By: Will Norris Facebook has a policy to not have closing ?> tags at the bottom of PHP files. It can unintentionally introduce newlines which causes ridiculous bugs. This is recommended in the Zend style guide: http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html
* [ Upgrading php-openid test framework to use PHPUnit 3.3 ]Luke Shepard2009-05-2737-250/+215
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Reviewed By: Will Norris The set of tests assumes PHPUnit 2.3, which conflicts with my environment setup. I think PHPUnit 3.3 is pretty widespread now, and under active maintenance (latest rev 4/10/2009). There's a few changes included here. I did a few mostly automated code transformations: replace "PHPUnit_TestCase" "PHPUnit_Framework_TestCase" replace "PHPUnit_TestSuite" "PHPUnit_Framework_TestSuite" removed all require_once "PHPUnit.php" - they are unnecessary. "call by reference" is now deprecated, so changed "&$" to "$" I also made a few changes to admin/testtext.php and Tests/TestDriver.php to accomodate the new syntax. Note that this just upgrades the framework; it does not guarantee that all tests pass. I'll submit future diffs to fix or disable failing unit tests. I wasn't able to get the tests running with the previous version, so I don't know if these have always been failing. I doubt that the github has automatically running unit tests, but if so then we'll have to make sure that the central repo is running the same version of PHPUnit.
* rewordingBrian Ellin2009-02-151-2/+2
|
* Merge branch 'master' of git@github.com:bce/php-openidGrant Monroe2009-02-141-0/+7
|\
| * typoBrian Ellin2009-02-141-1/+2
| |
| * typoBrian Ellin2009-02-141-1/+1
| |
| * added README.gitBrian Ellin2009-02-141-0/+6
|
* [project @ Unify method signatures to reduce E_STRICT warnings]tailor2008-12-122-2/+2
|
* [project @ Move signed assertions code into contrib/]tailor2008-12-082-0/+0
|
* [project @ OpenID Signed Assertions(Implementation of old sxip draft)]tailor2008-11-142-0/+400
| | | | | | | | | | | | | | | | | | | | | | | | | | In our solution, one party, which we call the Attribute Provider (AP), provides a signed certificate that the the user possesses some attribute (e.g. is over 18). This certificate is stored as an attribute at the user's OP, and other RPs can request this certificate when they want to verify attributes of the user. For the implementation, we have followed the OpenID Signed Assertions draft: http://www.mail-archive.com/specs@openid.net/msg00907.html The Signed Assertions Draft did not specify how signed assertions are stored at the OP, so we adopted the following scheme: Attribute: http://X Certificate: http://X/signature This enables RPs that don't care about certificates to completely ignore them. Assertions are SAML documents as specified in the OpenID Signed Assertions old draft. We are developing a demo application in which a university issues certificates verifying students' age, student-hood, and even their photo (also potentially useful to dating sites). So basically the university acts as an attribute provider, signing assertions about user claims. These claims are stored as an attribute in the OpenId provider and we can use the OpenID AX protocol to pass assertions as attributes. The data flow is: User requests assertion --- University(Attribute provider) --- (store request) --- Openid provider Relying Party(Dating site) --- (fetch request) --- OpenID Provider The RP gets the assertion, verifies the signature, and takes actions depending on the result. In some scenarios, the RP may deny the user request if the attribute verification fails (e.g. the dating site may forbid users under 18). In other scenarios the RP may treat them differently (e.g. the dating site could tag certified photos as "Verified Photo"). Note that the RP must have some sort of trust relationship with the AP. We've tried to keep the system as open as possible. Our protocol and implementation do not specify how this trust relationship is created or managed. For example, there could be a PKI specifically set up for verifying claims about student-hood, another trust system set up for verifying claims about age, etc. Santosh Subramanian Shishir Randive Michael Hart Rob Johnson
* [project @ Message: indentation]tailor2008-11-071-2/+2
|
* [project @ getAliasedArg() returns OpenID namespace when $aliased_key is 'ns']tailor2008-11-071-0/+5
| | | | | | | | | | This fixes an rather cryptic error when using stateless mode via the DumbStore. The 'ns' key can not be found in the alias/namespace mapping (its stored as the "Null Namespace"), it must be returned explicitly. The inability to find the key in the mapping results in a "Server Denied check_authentication" error, but the error is caused before any callback to the server is made. This also brings the PHP lib more in line with the ruby and python libs.
* [project @ Don't use Range header for ID page requests]tailor2008-10-312-4/+0
|
* [project @ Update version to 2.1.2]Kevin Turner2008-09-091-1/+1
|
* [project @ If we're generating user_setup_urls, let's at least do it correctly]tailor2008-07-112-6/+15
|
* [project @ Provide the user_setup_url in the Auth_OpenID_SetupNeededResponse ↵tailor2008-07-101-1/+3
| | | | even in OpenID 2]
* [project @ Demo server: remove stale HMACSHA1.php include]Kevin Turner2008-07-081-1/+0
|
* [project @ Update version to 2.1.1]Kevin Turner2008-06-271-1/+1
|
* [project @ Make the detect script work with 206 responses from the fetcher]Kevin Turner2008-06-251-3/+4
|
* [project @ Added a script that helps to update the valid TLD list for trust ↵Kevin Turner2008-06-251-0/+47
| | | | root matching]
* [project @ Updated TLD list in TrustRoot.php]Kevin Turner2008-06-251-13/+18
|
* [project @ remove Auth_OpenID::quoteMInimal. Resolves #262.]Kevin Turner2008-06-251-32/+0
|
* [project @ ↵dAniel hAhler2008-06-221-14/+6
| | | | | | | | | | ParanoidHTTPFetcher-strpos-instead-of-preg_match-and-code-improvements] ParanoidHTTPFetcher: - Fix corner case in get() and post() for headers without any value (e.g. 'Expires:') - Use strpos() instead of preg_match() when looking for ":" (and look for ": " now instead)
* [project @ fix accept header]tailor2008-06-231-1/+1
|
* [project @ Do not attempt HMAC-SHA256 tests if HMAC-SHA256 is not supported]http://j3h.us/2008-06-201-3/+7
|
* [project @ Fix Consumer's OpenID 1 checkid_immediate failure handling ↵http://j3h.us/2008-06-201-1/+2
| | | | (thanks to Evan Prodromou)]
* [project @ Test and fix HMAC-SHA256]http://j3h.us/2008-06-203-11/+46
|
* [project @ Rename files and tests related to HMACSHA1 and HMACSHA256]http://j3h.us/2008-06-2011-31/+36
|
* [project @ etxrd.getCanonicalID: case-insensitive comparsions, patch from =wil]Kevin Turner2008-06-131-8/+8
| | | | | | | 1. There should only be a single CanonicalID in each XRD (in the latest XRI resolution spec), so I made it use the first CID found instead of the last. 2. Use case-insensitive comparison when comparing CanonicalIDs.
* [project @ Accept response code 206 from fetcher results (part 2). Fixes #260]Kevin Turner2008-06-112-3/+3
|
* [project @ Accept response code 206 from fetcher results. Fixes #260]Kevin Turner2008-06-112-5/+7
|
* [project @ Add test cases for trust roots with non-ASCII characters in path ↵tailor2008-06-111-1/+3
| | | | or hostname]
* [project @ Auth_OpenID_urinorm: fail to parse URIs with non-ASCII characters]tailor2008-06-112-0/+26
|
* [project @ examples/discover: import consumer/common.php to set include_path]tailor2008-06-061-0/+3
|
* [project @ Add examples/discover.php tool]tailor2008-06-063-0/+103
|
* [project @ Do not send namespace aliases for extensions with OpenID 1 ↵tailor2008-06-063-2/+53
| | | | | | | | messages that we create] This makes the library compatible with the 1.x series of this library, since it did not handle arbitrary query keys with dots in them (PHP mangles . to _)
* [project @ demo RP: indentation]tailor2008-06-061-25/+25
|
* [project @ demo RP: escape response information prior to output]tailor2008-06-061-10/+21
|
* [project @ message: allow two values for OPENID1_NS]Kevin Turner2008-06-065-36/+213
| | | | | | | message: allow two values for OPENID1_NS Also: * fix op_endpoint bug in Server.php * always treat OpenID 1 namespace as implicit in messages we create
* [project @ Auth_OpenID_AuthRequest: simplify message construction]Kevin Turner2008-06-051-2/+1
|
* [project @ Change Auth_OpenID_VERSION to 2.1.0]tailor2008-06-051-1/+1
|
* [project @ Update CHANGES-2.1.0]tailor2008-06-051-2/+2
|
* [project @ add CHANGES-2.1.0]tailor2008-06-051-0/+50
|
* [project @ Deprecate Auth_OpenID_CheckIDRequest::namespace and stop using == ↵Kevin Turner2008-06-052-23/+37
| | | | Auth_OpenID_OPENID1_NS anywhere in server]
* [project @ add test for Auth_Yadis_getCanonicalId with subsegments]tailor2008-06-052-0/+66
|
* [project @ Plain http fetcher: allow for absent "path" key in parsed URL array]tailor2008-06-051-0/+4
|
* [project @ Auth_Yadis_Yadis::discover: Correctly test for null fetcher ↵tailor2008-06-051-1/+1
| | | | parameter]
* [project @ Auth_OpenID_getAllowedReturnURLs: use fetcher parameter in call ↵tailor2008-06-051-1/+1
| | | | to getServiceEndpoints]
* [project @ Fix Auth_OpenID_getAllowedReturnURLs, ↵tailor2008-06-053-6/+116
| | | | Auth_Yadis_DiscoveryResult::usedYadisLocation, add Auth_Yadis_getServiceEndpoints, tests]
* [project @ TestDriver.php: load "_other" tests regardless of primary test ↵tailor2008-06-051-6/+8
| | | | class type]
* [project @ handle empty string for trustroot the same as missing]tailor2008-06-052-11/+30
|
* [project @ #204 MalformedTrustRoot returned by the library now gets passed ↵tailor2008-06-052-1/+14
| | | | the OpenID Message object instead of null]
* [project @ Silence session_start warnings that are output for older builds ↵tailor2008-06-051-1/+1
| | | | of PHP 4.3 so the build passes]
* [project @ Add an explicit test for doubled-up ports for PHP 4.3 where the ↵tailor2008-06-051-0/+4
| | | | URL parsing is different]
* [project @ #229 Server.php: test hasReturnTo() when message=null]tailor2008-06-042-2/+10
|
* [project @ Add HTTP case to trustroot test cases]Kevin Turner2008-06-041-1/+2
|
* [project @ Auth_OpenID_Decoder::defaultDecoder: Check for ↵Kevin Turner2008-06-041-0/+6
| | | | Auth_OpenID_FailureResponse when getting OpenID message mode]
* [project @ Auth_OpenID_Decoder::decode: Check for ↵Kevin Turner2008-06-041-0/+5
| | | | Auth_OpenID_FailureResponse when getting OpenID message mode]
* [project @ #189 Add optional form_tag_attrs arg to ↵tailor2008-06-041-2/+3
| | | | Auth_OpenID_ServerResponse->toFormMarkup]
* [project @ Add an extra parsehtml testcase - no close script tag]tailor2008-06-041-0/+4
|
* [project @ fix typo in test data]tailor2008-06-041-1/+1
|
* [project @ Fix #220: Use return_to from request when generating form markup ↵tailor2008-06-042-2/+18
| | | | in Server.php]
* [project @ Test Server.php fix the error message if test_nomode fails]tailor2008-06-041-1/+1
|
* [project @ Port the v2 plaintext encryption test from python]tailor2008-06-041-0/+43
|
* [project @ Fix trust root test runner and then all failing tests that were ↵tailor2008-06-044-29/+75
| | | | exposed]
* [project @ Auth_OpenID_CheckIDRequest::fromMessage: return ↵Kevin Turner2008-06-042-15/+46
| | | | Auth_OpenID_ServerError if claimed_id is provided without identity]
* [project @ Auth_OpenID_Decoder::decode: make sure Auth_OpenID_ServerError ↵Kevin Turner2008-06-042-0/+34
| | | | has an Auth_OpenID_Message after encountering invalid OpenID namespace]
* [project @ #224: Tests_Auth_OpenID_CheckID: more test cases for missing ↵Kevin Turner2008-06-041-0/+30
| | | | trust_root/realm]
* [project @ Message->getArg & friends return FailureResponse on error]tailor2008-06-047-60/+94
|
* [project @ Add comment for Consumer::Response describing display_identifier ↵tailor2008-06-031-0/+17
| | | | and identity_url]
* [project @ rename return_to to current_url in Consumer.complete]tailor2008-06-031-4/+12
|
* [project @ server..Decoder.defaultDecoder: more readable error message]Kevin Turner2008-06-031-1/+1
|
* [project @ Add AX FetchResponse tests, fix bugs]tailor2008-06-032-1/+54
|
* [project @ AX::FetchResponse::fromSuccessResponse - return null when there's ↵tailor2008-06-032-1/+29
| | | | no ax args]
* [project @ 'fix' regexp looking for bad constant capitalization to allow ↵tailor2008-06-031-1/+1
| | | | NULL in strings]
* [project @ Add NOT NULL constraints to SQL stores]tailor2008-06-032-14/+20
|
* [project @ Fix PHP tags]tailor2008-06-035-2/+12
|
* [project @ Move MemcachedStore back from contrib, update license and copyright]tailor2008-06-033-44/+55
|
generated by cgit v1.1 at 2025-05-10 21:45:32 +0000