# BETA HOTFIX-001
## Default Test Credentials Verification

You are implementing Beta Hotfix-001 for the INVEETAIRE platform.

This is a bug fix.

This is NOT a feature.

Do NOT modify authentication architecture.

Do NOT redesign users.

---

Current Environment

Development URL:

http://localhost/inveetaire/

Production target:

https://inveetaire.com/

The application must continue working correctly in the localhost/inveetaire subfolder.

Do NOT hardcode localhost.

Do NOT change BASE_PATH handling.

---

Problem

The default test accounts cannot authenticate consistently.

Verify the complete authentication flow.

Determine whether the issue is:

- incorrect seed data
- incorrect password hashing
- username/email lookup
- authentication logic
- session handling

Fix ONLY the actual defect.

---

Default Accounts

The following accounts MUST exist and be usable.

Platform

Super Admin

Username:
admin

Password:
admin

Role:
Super Admin

Workspace:
NULL

Status:
Active

----------------------------------------

Workspace

Owner

Username:
test

Password:
test

Role:
Owner

Workspace:
test-couple

Status:
Active

If the workspace "test-couple" does not exist,
create it using the existing provisioning flow.

Do NOT bypass WorkspaceService.

---

Password Requirements

The stored password must be generated using the existing password_hash() implementation.

Never store plain text passwords.

If existing seed passwords are invalid,
regenerate them.

Update the seed data accordingly.

Do NOT change the authentication algorithm.

---

Database

Verify the seed.sql data.

If required,
update the seeded password hashes.

Do NOT manually insert inconsistent records.

Seed data must remain idempotent.

---

Verification

Verify:

admin / admin

test / test

Wrong password

Unknown username

Inactive account

Workspace assignment

Active workspace session

Session regeneration

Logout

Remember Me (if implemented)

---

Development Verification

Verify using:

http://localhost/inveetaire/

Confirm:

/admin login

/couple login

Legacy /login redirect

Session creation

Redirect after login

---

Constraints

Do NOT:

Modify routing

Modify Workspace architecture

Modify permission model

Modify business modules

Modify database schema

Implement new features

---

Acceptance Criteria

PASS only if:

admin/admin logs in successfully.

test/test logs in successfully.

Passwords are securely hashed.

Seed data updated if necessary.

Authentication remains unchanged.

Session behaves correctly.

Development environment localhost/inveetaire verified.

PHP syntax passes.

---

Output

Provide:

1. Files modified.

2. Root cause analysis.

3. Authentication fix.

4. Seed data changes.

5. Verification results.

6. Acceptance checklist.

7. PHP syntax results.

Stop after implementation.

Wait for Human Approval.