Skip to content

Conversation

@amulet1
Copy link
Contributor

@amulet1 amulet1 commented Jul 8, 2025

@ralflang: This PR is opened instead of #27 (to utilize a different source branch).

The verification code in verifySignedUrl and verifySignedQueryString methods expects the $data string to be in the following format: {url_with_timestamp}&_h={hash}. The supplied hash is checked against the hash computed on {url_with_timestamp}&_h= part.

However, both signUrl and signQueryString add an extra = (only in case if the supplied parameter is an instance of Horde_Url class), i.e. a hash is computed on {url_with_timestamp}&_h==, and the subsequent verification fails.

This is required (but not enough) in order to resolve horde/base#12.

@amulet1
Copy link
Contributor Author

amulet1 commented Aug 6, 2025

@TDannhauer, please could you review/merge?

@TDannhauer TDannhauer merged commit 71c808f into horde:FRAMEWORK_6_0 Aug 13, 2025
0 of 4 checks passed
@amulet1
Copy link
Contributor Author

amulet1 commented Aug 15, 2025

Once horde/Url#4 is approved, changes in signUrl() and signQueryString() will be needed again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Messed up URL when redirecting to auth during login or refresh

2 participants