You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thank you for your hard work on this project.
I have deployed your project and I am using it, I have a basic question.
I have two clients, for example, client A and client B. Now, when I log in with client A, I don't want to allow the user to log in to client B, because when I go to client B, I can use client B through a silent login. and IDP doesn't stop client B from logging in. In fact, I want to assign each user to client properties so that a user who doesn't have access to client B can't use it.
Should this be done only through Role or something like scope?
How can I prevent such a problem?
Is there a default solution for this issue in Identity Server or not?
If there is, should it be handled on the IDS side or on the client side?
The text was updated successfully, but these errors were encountered:
masoodafar-web
changed the title
Limiting the use of one session in two clients Hello, thank you for your hard work on this project. I have deployed your project and I am using it, I have a basic question. I have two clients, for example, client A and client B. Now, when I log in with client A, I don't want to allow the user to log in to client B, because when I go to client B, I can use client B through a silent login. . How can I prevent such a problem? Is there a default solution for this issue in Identity Server or not? If there is, should it be handled on the IDS side or on the client side?
Limiting the use of one session in two clients
Jul 12, 2023
Hello, thank you for your hard work on this project.
I have deployed your project and I am using it, I have a basic question.
I have two clients, for example, client A and client B. Now, when I log in with client A, I don't want to allow the user to log in to client B, because when I go to client B, I can use client B through a silent login. and IDP doesn't stop client B from logging in. In fact, I want to assign each user to client properties so that a user who doesn't have access to client B can't use it.
Should this be done only through Role or something like scope?
How can I prevent such a problem?
Is there a default solution for this issue in Identity Server or not?
If there is, should it be handled on the IDS side or on the client side?
The text was updated successfully, but these errors were encountered: