Hello,
I see your points, fair enough. For future-this-feature-seekers, we will create a new solution with community edition, apply our solution and push it to a new repo at https://github.com/kkeld/CommunityNova . Deleted the repo, closed the question.
Best.
Hello again,
I guess there is a misunderstanding. We did not want you to implement anything for us. There are similar questions like [1], [2]. The usual flow we observed is that: customer asks a question, you ask for clarification, customer elaborates, you ask for sample code, customer gives sample code, you guide them through code. We just wanted to cut that piggy back by supplying a repo with minimal changes only related to the feature we are asking for. We tried explaining what we want and where we failed clearly. We were just expecting some guidance like you yourself requested your colleague and he did so for the issue at [3]. Since we could not get anything new for this question, would you consider amending our question token back?
Anyway, meanwhile we managed to get this working. We updated the repo at [4] in case someone else needs it, too.
Hello!
We are trying to prevent users logging in from different computers with the same account. You have provided a sample project (1), but it is implemented with Identity Server and MVC (2).
We have tried to adjust it to our needs (OpenIddict + Angular). Currently, we can detect when a second client logs in with the same account using a claim. Unfortunately, we could not manage to successfully log out the previously logged in user and redirect the application to the login page. At this point, we are stuck at getting a 403 response.
We have created a sample project using ABP Suite with all the default options. This project has the same structure as our main project and can be used as a minimal reproducible example. Could you give us some directions to make this work the right way? Our efforts can be seen in the commit (4). If needed, we can give you contributor privileges to the repository.
Thanks!