Parent node: OIDplus makeAuthKey / makeSecret realms (oidplus/authRealms)
UUID: | bb1aebd6-fe6a-11ed-a553-3c4a92df8582 |
C++ notation: | { 0xbb1aebd6, 0xfe6a, 0x11ed, { 0xa5, 0x53, 0x3c, 0x4a, 0x92, 0xdf, 0x85, 0x82 } } |
Variant: | [0b10_] RFC 4122 (Leach-Mealling-Salz) / DCE 1.1 |
Version: | [0x1] Time-based with unique host identifier |
Timestamp: | [0x1edfe6abb1aebd6] 2023-05-29 21:49:47'7445590 GMT |
Clock ID: | [0xa553] 9555 |
Node ID: | [0x3c4a92df8582] 3C-4A-92-DF-85-82 |
Input: | 3C-4A-92-DF-85-82 |
Type: | EUI-48 (Extended Unique Identifier) |
EUI-48 or MAC-48: | 3C-4A-92-DF-85-82 |
EUI-64: | 3C-4A-92-FF-FF-DF-85-82 (MAC-48 to EUI-64 Encapsulation) |
IPv6-Link-Local address: | fe80::3e4a:92ff:fedf:8582 |
Administration type (U/L flag): | [0] Universally Administered Address (UAA) |
Transmission type (I/G flag): | [0] Unicast (Individual) |
The JWT additionally contains a member oidplus_ssh = OIDplus::authUtils()->makeSecret(["bb1aebd6-fe6a-11ed-a553-3c4a92df8582"]
(SSH = Server Secret Hash) with the sole purpose of allowing to invalidate all issued JWT by changing the server secret. (This would be more secure than the Blacklist feature, since changing the server secret) also invalidates JWT which might have been maliciously postdated).