Releases · portier/portier-php

01 Dec 10:55

stephank

v0.6.0 Latest

Latest

BREAKING: This PR reverts the API change made to the verify method in v0.5.0:
```
-public function verify(string $token): VerifyResult
+public function verify(string $token): string
```
v0.5.0 mistakenly assumed state was part of the token, but it is simply returned in a query parameter state to the callback / redirect URI. As such, your application can extract it directly from the request.

Assets 2

29 Nov 18:46

stephank

v0.5.0

The authenticate method now takes an optional second argument $state, which is returned by verify in your callback:

-public function authenticate(string $email): string
+public function authenticate(string $email, string $state = null): string

BREAKING: The verify method now returns an object, so that it can also return the original $state from the call to authenticate:
```
-public function verify(string $token): string
+public function verify(string $token): VerifyResult
```

Assets 2

21 Dec 14:00

stephank

v0.4.2

Assets 2

05 May 15:31

stephank

v0.4.1

The Client::leeway property is now properly applied when validating tokens. This was previously not the case, resulting in zero leeway.
The authorization_endpoint from the discovery document is now properly applied, instead of hardcoding the /auth broker route. This means Client::authenticate() now does an external HTTP request, but caching should not change the overall amount of requests made by the client.

Assets 2

12 Apr 12:05

stephank

v0.4.0

This version requires PHP 7.4 or 8.0.
Client::normalize() now takes a single string email address, instead of an array. This is because recent PHP versions have all the functionality required to do normalization locally, and we no longer have to fall back to calling the Portier broker HTTP API. The fallback code has been removed, as well as normalizeLocal and hasNormalizeLocal.
Function return types have been added to StoreInterface and AbstractStore. Custom store implementations may have to be adjusted to match, but this should not require any change in the implementation.