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

When we are using the expired token from session logout api then token not expired/disabled from admin panel #45

Open
komal-sh-27 opened this issue May 19, 2023 · 0 comments
Labels
Bug Something isn't working Fixed Proposed Regarding PR is already created for this issue V-1.1.x Regarding issue v-1.1.x

Comments

@komal-sh-27
Copy link

Description
When we are using the expired token from session logout api then token not expired/disabled from admin panel

How to reproduce
Step 1: First create a token from using session login api or from admin panel on admin credentials button:

image

Step 2: Now we have api token expired from session logout api using postman side:

Headers:

{
    "Authorization": "Bearer ACCESS_TOKEN"
}

Step 3: After token expired now check on the admin panel and here this token still enabled:

image

Possible Solution

If we have api token expired from session logout api side so here should be token is expired like when click on disbaled button so here status is disabled but here should be status shown expired and also enabled button is unclickable so that we are not able to status is enabled again:

image

Note: Discussed with Akshay Sir

@komal-sh-27 komal-sh-27 added the Bug Something isn't working label May 19, 2023
@komal-sh-27 komal-sh-27 added the V-1.1.x Regarding issue v-1.1.x label Jun 8, 2023
Abhi12-gupta added a commit to Abhi12-gupta/api-bundle that referenced this issue Jun 15, 2023
@komal-sh-27 komal-sh-27 added the Fixed Proposed Regarding PR is already created for this issue label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Fixed Proposed Regarding PR is already created for this issue V-1.1.x Regarding issue v-1.1.x
Projects
None yet
Development

No branches or pull requests

1 participant