auth_req_payload
and registering an account with the HAS, the PKSA will start to receive registered account authentication request with the message:data
: the Base64 representation of an encrypted auth_req_data
objectuuid
: the request identifierexpire
: UNIX time when the request will expireauth_req_data
is:app
: an object describing the applicationname
: short name of the app (ex: "peakd")description
: (optional) description of the app (ex: "Peakd for Hive")icon
: (optional) URL to retrieve the application icon (ex: "https://peakd.com/logo.png"
)token
: (optional) a valid session token previously received from the PKSAchallenge
: (optional) a challenge_data
object that the app can pass to the PKSA for signing (see Challenge request).auth_req_data
object using the encryption key previously shared with the PKSA (auth_key
). By encrypting the auth_req_data
object, the HAS will be unaware of what's going on between the app and the PKSA and unable to tamper with the authentication request process.uuid
found in the auth_req
message matches the one from the auth_req_payload
and ignore any message with a mismatching uuid
auth_req
message)