[Bug]: Custom Storage to use Memory throw exception

[mohsenvafa]

Version

19.0.0

when you create a custom storage to use memory, authentication state is not persist and throw error:
Error in loading user info: Error: could not find matching config for state b6c6e5619e6a955d6cbc....

Steps to reproduce the behavior

create a custom storage as below and provide the storage class in a module using the providers array
{ provide: AbstractSecurityStorage, useClass: MemoryStorageService }

import { Injectable } from '@angular/core';
import { AbstractSecurityStorage } from 'angular-auth-oidc-client';

@Injectable()
export class MemoryStorageService implements AbstractSecurityStorage {
  private data = new Map<string, string>();
  read(key: string) {
    return this.data.get(key) || null;
  }

  write(key: string, value: any): void {
    this.data.set(key, value);
  }

  remove(key: string): void {
    this.data.delete(key);
  }

  clear(): void {
    this.data.clear();
  }
}

[Salketer]

When you do authentication, unless using popup, the user leaves the page and comes back. When leaving, javascript memory is wiped.

[mohsenvafa]

When you do authentication, unless using popup, the user leaves the page and comes back. When leaving, javascript memory is wiped.

That makes sense. Is there a way to store at least the access or ID token in memory instead of using persistent storage like LocalStorage or SessionStorage?

[Salketer]

No.

…

On Tue., Apr. 1, 2025, 19:22 Mohsen Vafa, ***@***.***> wrote: When you do authentication, unless using popup, the user leaves the page and comes back. When leaving, javascript memory is wiped. That makes sense. Is there a way to store at least the access or ID token in memory instead of using persistent storage like LocalStorage or SessionStorage? — Reply to this email directly, view it on GitHub <#2064 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVM2ZT7WQHHEWJKYELCM732XLDM7AVCNFSM6AAAAABVEFKI62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZQGEZDGNZZGU> . You are receiving this because you commented.Message ID: ***@***.***> [image: mohsenvafa]*mohsenvafa* left a comment (damienbod/angular-auth-oidc-client#2064) <#2064 (comment)> When you do authentication, unless using popup, the user leaves the page and comes back. When leaving, javascript memory is wiped. That makes sense. Is there a way to store at least the access or ID token in memory instead of using persistent storage like LocalStorage or SessionStorage? — Reply to this email directly, view it on GitHub <#2064 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVM2ZT7WQHHEWJKYELCM732XLDM7AVCNFSM6AAAAABVEFKI62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZQGEZDGNZZGU> . You are receiving this because you commented.Message ID: ***@***.***>