Story #3666

D1Client.listUpdateHistory() needs to handle changing access policies

Added by Rob Nahf about 11 years ago. Updated about 6 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Story Points:


the current D1Client.listUpdateHistory() method needs to gracefully handle the situation where a NotAuthorized request is returned. the ObsoletesChain client class may need to be refactored to allow for this exception to be held so it can notify the user where appropriate.

Ostensibly, with a NotAuthorized, the user will not have access to either the tail or head of the chain, so can't return the head or tail, depending on how access changes.


#1 Updated by Rob Nahf about 11 years ago

  • % Done changed from 0 to 30
  • Status changed from New to In Progress

will add a boolean or exception column to the Object[] in the ObsoletesChain class, to annotate problems in chain traversal.

#2 Updated by Rob Nahf over 9 years ago

  • Due date set to 2014-10-01
  • Target version set to Release Backlog
  • Start date set to 2014-10-01

#3 Updated by Rob Nahf about 9 years ago

  • Category changed from d1_libclient_java to d1_libclient_java
  • Target version changed from Release Backlog to CLJ
  • Project changed from Infrastructure to Java Client

Is this a v1 libclient-only issue? or is this method valuable for interaction with v1 MNs?

The solution might only belong in v1 libclient, but I'm not sure..

#4 Updated by Rob Nahf about 9 years ago

  • Target version deleted (CLJ)

#5 Updated by Dave Vieglais about 6 years ago

  • Priority changed from Normal to Low

#6 Updated by Dave Vieglais about 6 years ago

  • Sprint set to Infrastructure backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)