Topic
Digital Identity and Credentials
Within the Topic facet, Digital Identity and Credentials topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Asia-Pacific Institutional
TrueMoney's Banking Entry Is Still Conditional, Not Effective
Approval by Thailand's Finance Ministry on 19 June 2025 put the virtual-bank vehicle of TrueMoney's parent, Ascend Money, one step along a gated path. It did not produce a bank. The path still runs through incorporation as a public limited company, a Bank of Thailand readiness…
IETF
The Token Lasted Five Minutes. The Authority Behind It Did Not.
A purchasing agent received a credential for one invoice API, one transaction and no more than five minutes. The token looked admirably narrow. The refresh credential that could ask for the next token, however, still survived in the agent's vault. The clock had reduced exposure…
IETF
The Registry Copied Every Proof. It Still Could Not Make the Decision.
Two registries held the same signed agent record, the same route observation and the same evidence references. One bank admitted the agent to a low-risk task. Another refused it. The disagreement was not a replication failure; it was the decision the shared record was never…
IETF
The Server Said 200. The Request Was Still Pending.
The client sent a cancellation request and received the cleanest answer HTTP can provide: `200 OK`. It closed the case. The authorization server had never advertised support for cancelling deferred requests, however, and RFC 7009 required the same answer even when nothing…
IETF
The Key Rotated. The Agent's History Had to Stay Attached.
The signing key changed exactly as policy required. The old credential was revoked, the new one verified, and the service resumed without an error. Then the audit console opened a blank reputation record. The security ceremony had succeeded while the accountability system quietly…
IETF
The Score Survived Export. The Evaluation Claim Did Not.
The review packet contained the same number the evaluator had produced: 0.734. Its signature checked. Its run identifier matched. Yet the packet could not say whether the measurement had actually run, which metric the number belonged to, what population it described, or whether…
IETF
The Signature Stayed Small. The Evidence Chain Did Not.
The incident packet arrived with one compact cryptographic value at the end. It looked like a compressed audit trail. It was not. To verify it, the reviewer still needed every workload credential, every signature-input record, every preserved route value and every…
History
A Password Could Be Used Once. The Session Still Needed Its Own Protection: RFC 2444
RFC 2444 made a one-time password a named way for network protocols to authenticate a user. It did not make the conversation that followed private, prove who answered the server, or turn a successful login into a general security guarantee.
IETF
Two Valid Approvals. Zero Valid Quorums.
The approval counter reached two. The rule required two. The screen turned green. Yet one approval belonged to the committee before a member left and the other belonged to the committee after a replacement joined. No committee that actually existed had two approvals.
IETF
The User Approved the Sentence. The Expansion Record Was Outside the Signature.
Two evidence entities can preserve the same sentence, click and time, produce the same inner-signature input, and still tell incompatible stories about how “cheap headphones” became executable parameters. The cryptography has not failed. The signed entity is simply narrower than…
IETF
The Recovery Was Ready. Its Receipt Was Still Only a Promise.
A reconstructed asset can be usable before the evidence intended to witness its recovery exists. A new individual IETF draft gives that interval a precise name—unwitnessed—and forces operators to decide whether availability or auditability controls the release gate.
IETF
The Fake Account Number Was Private Enough to Cause a Real Refund
A customer-service record replaced an account number with a believable substitute. The original identifier was protected; the next agent could no longer tell that the visible number was invented. Privacy succeeded at concealment and failed at operational truth. A new VCON…
IETF
The Decision Crossed the Boundary. Only One Request Could Carry It
The permit is authentic. The presenter is known. Yet the payment body differs by one cent from the action the policy engine approved. A new Internet-Draft makes that tiny change decisive: the remote recipient should refuse before the permit is consumed, because a signed decision…
IETF
The Engine Said `allow_unresolved`. Nothing Was Authorised Yet
A policy engine recognises a time window, lacks a trusted clock and returns a structured list of unfinished obligations. The integration layer sees the word “allow”, converts the enum to a successful Boolean and releases the action. No rule was broken inside the engine. The…
IETF
The Log Had No Gaps. Its Last Pages Could Still Be Missing
A verifier receives receipts numbered zero through forty-two. Every signature checks, every running count agrees and no number is absent. The display says “complete.” That conclusion is one receipt too early: the holder may simply have withheld everything from forty-three onward.
IETF
The Header Looked Like an Access Token. The Authority Model Had Changed
The new DPoP credential draft makes an audaciously economical move: put a reusable issuer-signed Credential where an access token normally goes, then reuse the proof machinery unchanged. The bytes fit. The hard question is whether the verifier remembers that the authority behind…
IETF
One String Came Back. The OAuth Grant Was Still Unfinished
The new out-of-band OAuth draft solves a real human-interface problem with unusual restraint: instead of asking a remote-terminal user to copy both `code` and `state`, it makes one string. The danger begins when that cleaner handoff is mistaken for a stronger grant.
IETF
The Boolean Was Signed. The Chain State Had Already Moved
Wallet State Attestation revision 01 turns an issuer’s reading of on-chain state into a portable signed answer. Its strongest contribution is also its warning: signature, state anchor, freshness, finality and authorization remain different proofs.
IETF
An Agent Token Can Be Refused Without Revealing Which Grant Failed
A verifier may know exactly why an agent's delegation fails while the remote caller needs to know much less. A newly revised individual Internet-Draft puts that difference at the center of token refusal.
IETF
The Certificate Chain Passed. The Node ID Still Had Another Gate
Revision 11 of an IETF DTN draft puts Endpoint ID sets into configuration and X.509 certificates. Its most consequential rule is easy to miss: ordinary certificate-path validation does not decide whether the concrete node belongs to the permitted set.