HiveAuth
Search…
Attach
At any time, a connection between the APP and the HAS infrastructure may be interrupted. It is then important that the APP can reconnect and know if a request that it sent to the HAS has already been processed by a PKSA or is still pending.
Fortunately, the HAS protocol has a feature to resume such interaction.
When an APP wants to resume a broken session, it can ask the HAS to reconnect its socket with the request identifier previously received. To do so, the APP sends the following message:

attach_req

1
{
2
cmd: "attach_req",
3
uuid: string
4
}
Copied!
Properties
  • uuid {string} the request identifier
If the request has not expired, the HAS server will confirm the reconnection with the following message:

attach_ack

1
{
2
cmd: "attach_ack",
3
uuid: string
4
}
Copied!
Properties
  • uuid {string} the request identifier
If the request has expired, or if the answer that it received from the PKSA has expired, the HAS server will inform the APP that it no more manage the request with the following message:

attach_nack

1
{
2
cmd: "attach_nack",
3
uuid: string
4
}
Copied!
Properties
  • uuid {string} the request identifier