The Partner → login seam (PA-AUTHZ E-09). The SDK ships no users table
and — by hard invariant — makes no assumption about the auth table. So it never
reads or writes the host login directly: it declares this port, the host binds the
adapter (an EloquentLoginProvider over its own users row keyed by the
users.partner_id bridge).
The symmetric complement of {@see \LaravelUi5\Sdk\Partners\Contracts\HasPartnerInterface}
(which maps auth()->user() → Partner); this maps Partner → login. Whatever the host's
auth store, every method speaks {@see LoginRecord} — the SDK's own concrete DTO — never a
host User model.
The account/RBAC lifecycle stops here: deleting a login never deletes the partner (the partner is the durable actor its assignments belong to). Ending those assignments on delete is the caller's concern (PA-AUTHZ D8), not the provider's.
| Methods | ||
|---|---|---|
public
|
forPartner(int $partnerId): ?LoginRecord
|
# |
public
|
attachedPartnerIds(): int[]
|
# |
public
|
create(int $partnerId, string $email, string $password): LoginRecord
|
# |
public
|
setLocked(int $partnerId, bool $locked): void
|
# |
public
|
resetPassword(int $partnerId, string $password): void
|
# |
public
|
delete(int $partnerId): void
|
# |