Difference between revisions of "Persistent"
From MgmtWiki
(→References) |
(→References) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
==References== | ==References== | ||
<references /> | <references /> | ||
| − | * On this wiki [[Persistent Connection Management]] | + | * On this wiki see [[Persistent Connection Management]] |
| + | * On this wiki see [[Object Permanence]] | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
[[Category:Identifier]] | [[Category:Identifier]] | ||
| − | |||
| − | |||
Latest revision as of 13:51, 8 October 2022
Full Title or Meme
When an entity has a Persistent Identifier the assumption is that the Behavior of the entity will remain consistent over time.
Context
- An Identifier's primary function is to create a label to which attributes can be attached.
- For an otherwise anonymous connection to enable attribute checking, like the User's that are over 13, 18, or 21 years of age, some ephemeral Identifier is needed to ensure that any verified attribute cannot be reused in some other context.
- Ephemeral Identifiers are the antonym of Persistent Identifiers.
Problem
Many protocols, like OpenID Connect supply a Subject Identifier (sub) that is meant to reflect the same Subject over a period of time. Typically those protocols permit transitory binding of the Identifier to a real world entity.
References
- On this wiki see Persistent Connection Management
- On this wiki see Object Permanence
