spryker/customer

Included commits: 7.81.1...7.82.0

Improvements

• Declared HTTP response codes for the customer registration confirmation endpoint to support API discoverability for the Storefront API.

Fixes

• Corrected the registration confirmation response code declaration from 200 to 201 and simplified the 422 description to cover both unknown keys and already-confirmed accounts, replacing separate 404 and 409 entries.

Included commits: 7.81.0...7.81.1

Adjustments

• Registered SprykerTest\Zed\Customer\Helper namespace in the autoloader to home test doubles in their seam-owning module.

Included commits: 7.80.2...7.81.0

Improvements

• Extended CustomerFacadeInterface::getCustomer() with an optional $isSecure parameter; when true (default), the password hash is excluded from the returned transfer to improve authentication security.
• Introduced CustomerClientInterface::getCustomerForAuthentication() to retrieve the customer including the password hash exclusively for authentication contexts.
• Adjusted CustomerSession::setCustomer() and setCustomerRawData() to exclude the password hash from the session to improve authentication security.
• Adjusted AbstractSpyCustomer::toArray() to strip the password field by default, and AbstractSpyCustomer::setPassword() to guard against accidental null overwrites on existing entities.

Included commits: 7.80.1...7.80.2

Fixes

• Fixed Customer::attachAddresses() to pass a non-null Criteria to bypass Propel's instance-pool cache, preventing stale empty address collections from being returned in long-running FPM workers.

Included commits: 7.80.0...7.80.1

Fixes

• Reverted broken release.

Included commits: 7.79.0...7.80.0

Improvements

• Introduced CustomerClientInterface::getCustomerForAuthentication() to retrieve customer data including the password hash exclusively for authentication contexts, keeping credential validation separate from general customer data retrieval.
• Extended CustomerFacadeInterface::getCustomer() with an optional $isSecure parameter (defaults to true) to exclude the password hash from the returned CustomerTransfer by default, ensuring credentials are not inadvertently exposed outside authentication flows.
• Adjusted update(), updatePassword(), findCustomerByReference(), and resolveCustomer() to strip the password hash from returned transfers, ensuring credentials are excluded from customer data used outside of authentication.

Included commits: 7.78.2...7.79.0

Improvements

• Extended customer search in the Back Office by adding support for filtering by first name, last name, and email using partial matching, enabling more flexible customer lookup in Back Office configuration.
• Introduced CustomerCriteriaSearchTerms transfer to carry search term filters (firstName, lastName, email) for customer queries.
• Added searchTerms and limit fields to CustomerCriteriaFilterTransfer to support configurable and targeted customer search.

Included commits: 7.78.1...7.78.2

Adjustments

• Removed includableIn declaration from customers-addresses resource schema file to align with the updated API Platform schema model.

Included commits: 7.78.0...7.78.1

Fixes

• Adjusted PHPStan configuration to use excludePaths instead of individual ignoreErrors entries for API Platform Storefront classes, fixing PHPStan errors.

Included commits: 7.77.0...7.78.0

Improvements

• Introduced CustomerFacade::resolveCustomer() and CustomerClient::resolveCustomer() to resolve or create a customer from OAuth resource owner data, supporting SOL-484 aim readiness in existing modules.
• Introduced AcceptOnlyOauthCustomerAuthenticationStrategyPlugin and CreateCustomerOauthCustomerAuthenticationStrategyPlugin to configure customer resolution behavior on OAuth login.
• Added sendRegistrationToken property to CustomerTransfer to control registration token delivery during OAuth-based customer creation.
• Introduced new transfers ResourceOwnerTransfer, ResourceOwnerRequestTransfer, ResourceOwnerResponseTransfer, OauthCustomerResolveRequestTransfer, OauthCustomerResolveResponseTransfer, OauthCustomerRestrictionRequestTransfer, and OauthCustomerRestrictionResponseTransfer to support OAuth customer resolution flow.