Search results

Jump to navigation Jump to search

Page title matches

  • ===Reports of Problems with Redress and Recovery Today=== ...ce these service are typically provided at no or low cast to the user, the recovery and redress functions are usually highly automated with manned support avai
    12 KB (2,064 words) - 19:21, 28 May 2020
  • 3 KB (539 words) - 19:16, 17 July 2018
  • Recovery of [[Identifier]]s that are bound to secrets, like private keys, are comple ...chitecture the identifier is created by the IdP and so that IdP can handel recovery entirely within their own organization. Some do it well.
    5 KB (755 words) - 00:44, 4 June 2020

Page text matches

  • ===Recovery and Redress===
    28 KB (4,415 words) - 17:28, 21 March 2021
  • * Redress & Recovery (including key and ID roll-over)
    30 KB (4,866 words) - 16:56, 9 June 2021
  • # Recovery of access - usually loss of access to one or more EHR - access to the recor
    20 KB (3,074 words) - 22:40, 21 March 2021
  • * In Healthcare not only are lives lost, but the paperwork required for recovery when patient records are lost is very large.
    5 KB (834 words) - 00:18, 24 August 2020
  • |puid || Persistent Identifier of RO || to handle recovery operation||MAY ...outside the scope of this document. That mechanism will need to handle the recovery of access where the sub's authenticator cannot be used for any reason.
    3 KB (586 words) - 17:33, 25 July 2020
  • |puid || Persistent Identifier of RO || to handle recovery operation||MAY ...outside the scope of this document. That mechanism will need to handle the recovery of access where the sub's authenticator cannot be used for any reason.
    7 KB (1,127 words) - 21:03, 15 April 2021
  • ...issues about sub and a persistent ID in the context of the problem of key recovery, reissue and roll-over while giving the user a better experience with OpenI * If the user's hardware device is stolen or disabled, the recovery of the user's identifier can be a challenge which could turn into a UX nigh
    6 KB (856 words) - 23:37, 25 July 2020
  • ...chitecture the identifier is created by the IdP and so that IdP can handel recovery entirely within their own organization. Some do it well. ...resolution to any kind of resolver and so have full responsibility for any recovery of loss of access to identifiers.
    3 KB (423 words) - 01:58, 4 June 2020
  • Recovery of [[Identifier]]s that are bound to secrets, like private keys, are comple ...chitecture the identifier is created by the IdP and so that IdP can handel recovery entirely within their own organization. Some do it well.
    5 KB (755 words) - 00:44, 4 June 2020
  • *[[User recovery and redress]] is dependent on no [[User Notice]] for operations.
    2 KB (291 words) - 16:16, 27 May 2020
  • #The user is asked for some means to contact them for recovery or redress, typically an email address or phone number.
    13 KB (2,156 words) - 18:55, 7 December 2020
  • #The user is asked for some means to contact them for recovery or redress, typically an email address or phone number.
    14 KB (2,290 words) - 21:36, 30 March 2020
  • # Recovery of access - usually loss of access to one or more EHR - access to the recor
    19 KB (2,997 words) - 01:34, 18 February 2021
  • * Recovery of access lost due to changes in the user's device must be addressed. See s ...fiable information. This is handled with the user experience components of recovery and redress which are described elsewhere.
    19 KB (3,008 words) - 20:23, 20 March 2021
  • ====Compliance and Recovery of User Identifiers==== ...his example assumes that contact with the user is required, also used for recovery. While it is possible for later reuse of the email name to cause a collisio
    24 KB (3,980 words) - 19:57, 13 November 2020
  • ...channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.
    2 KB (340 words) - 21:49, 27 April 2019
  • ...lains why registration is important before they can use the site (redress, recovery, etc.)
    8 KB (1,248 words) - 20:08, 4 December 2019
  • ...vice available for entities that do not normally interact with the user on recovery and redress
    5 KB (788 words) - 16:34, 16 April 2019
  • ...channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.
    7 KB (1,037 words) - 04:58, 22 April 2020
  • ...channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.
    8 KB (1,167 words) - 04:14, 28 September 2019

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)