Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: EventTypes.TokenExpired is fired whereas the token has been renewed #1747

Open
elvince opened this issue May 3, 2023 · 0 comments
Open

Comments

@elvince
Copy link

elvince commented May 3, 2023

Version

15.0.3

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

My code is routing to expired page component where as the token was properly renewed

Steps to reproduce the behavior

Here is the code I'm using to register the event:

 this.eventService
      .registerForEvents()
      .pipe(filter((notification) =>  notification.type === EventTypes.TokenExpired
      ))
      .subscribe((notification) => {
        switch (notification.type) {         
          //case EventTypes.TokenExpired:
          //  if (notification.value === true) {
          //    this.router.navigateByUrl("/expired");
          //  }
          //  break;
        }        
      });

A clear and concise description of what you expected to happen.

As long as the token is renewed, I shouldn't received any Tokenexpiration event.

There is another strange issue with this event:
When I shudown my autority server, the renew failed and the tokenexpired event is fired (expected) but not just once but multiple times.

Thanks for your help!

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant