Add a mechanism to explore / iterate through all generations of tokens issued for an OAuth2 or OIDC User session #66
Description
The debugger can already make N refresh token grant calls and report how many iterations of refresh grant calls have been made within a session. This ticket will enhance the existing functionality to keep track of all generations of the tokens that have been issued within the debugger application context. One will be able to navigate through the generations of OAuth2 Refresh Grant calls and view the tokens associated with that call. These tokens include the OIDC ID Token, OAuth2 Access Token, and OAuth2 Refresh Token. Any additional fields returned besides these tokens in the Refresh Token Grant Response should also be stored for each generation and displayed to the user when that generation of tokens is selected.
All of the functionality that is currently available in the Token Endpoint Results pane of the debugger2 screen should be available to each refresh token grants calls that can viewed.
When the user clicks RP-initiated Logout, all of the tokens should be deleted and the UI for debugger2 reset.
All tokens associated with the current session should be maintained in local storage until RP-Initiated Logout occurs or a new protocol session is initiated on the debugger1 screen. This will present itself as a new Authorization Code to the debugger2 screen. So, when authorization code is set in the UI, assume that means the debugger2 screen UI needs to be reset.
Until that event occurs, the user should be able to navigate to subscreens to use various functionality and return to debugger2 and be able to retrieve any token type from any refresh grant generation.