Generally, policyholders do not log in directly. Instead, Homeras coordinates with your insurer (such as AG Insurance ) to manage the repair process from request to finalization. Troubleshooting Common Login Issues If you have an existing account but cannot gain access:
The portal serves as a critical digital gateway for insurance companies, property managers, and service providers to coordinate repairs and technical interventions across Belgium. Accessing the Homeras Connect Portal homeras login
Homeras‑Auth v2 interaction diagram (OPAQUE + optional WebAuthn) Generally, policyholders do not log in directly
Ensure you are on the official Homeras.be site. Because the platform manages sensitive data (like national register numbers and technical device IDs), security is tight. | | 2 | Server → Client: Registration
![Figure1 placeholder]
| Step | Message | Cryptographic Operation | |------|---------|--------------------------| | | Client → Server: Registration Init | Client generates OPAQUE Registration Request (R1) . | | 2 | Server → Client: Registration Response | Server replies with R2 containing a salted envelope (encrypted with server’s public key). | | 3 | Client → Server: Registration Final | Client sends R3 containing encrypted password envelope (OPAQUE). Server stores the envelope. | | 4 | Client → Server: Login Init | Client sends Login Request (L1) (OPAQUE login start). | | 5 | Server → Client: Login Response | Server returns L2 containing server's public key and a nonce. | | 6 | Client → Server: Login Final | Client sends L3 with OPAQUE proof (zero‑knowledge). | | 7 | (Optional) MFA Challenge | If risk score > threshold, server issues push or FIDO2 challenge. | | 8 | Server → Client: Auth Token | Server issues JWT signed with RS256, includes cnf claim binding to tls-unique and device_fingerprint . | | 9 | Client → Server: Subsequent Requests | JWT presented in Authorization: Bearer header; server validates signature, expiry, and binding. |
[User Agent] --HTTPS POST--> [API GW] --gRPC--> [Auth Service] | | |<---SMS OTP---[SMS Provider] | | | <--Set-Cookie JWT---[API GW]---[User Agent]