Hi, please ignore it. I have fixed it by updating the Theme LeptonX version as well:
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="3.2.0" />
noted. Let me upgrade it to 8.2.0.
Thank you
Hi @maliming, Yes, I have enabled the feature. Could you let me know when this feature was officially released?
I created a new project using version 8.0.2, but noticed that the feature is not available. Interestingly, my older project, also on version 8.0.2, includes it. I'm not sure why there's this discrepancy.
Hi @maliming, this feature does not seem to work. After selecting the "LogoutFromAllDevices" option. I logged in on a new device, and observed that in the AbpSessions table, the old session was deleted and the new session has been created. However, the web application (I am using Angular) did not log me out on the old device.
Am I missing something? Could you help me resolve this?
I am working with the ABP Framework, and I came across a pattern in the code where a controller class is implementing an application service interface, as shown below:
Could you kindly clarify the reasoning behind this pattern? Specifically, why would a controller implement an application service interface, as it seems to merge the concerns of both the controller and the service layer into one class?
I understand that typically the application service encapsulates the business logic, while the controller handles the HTTP requests. Is this an intended pattern in certain scenarios within ABP, and what would be the advantages or trade-offs of using it compared to the more common separation of concerns?
I would like to implement a feature to disable concurrent user logins in our application to enhance security.
Requirements:
Most of the articles I found here is for Identity Server 4, I have migrated to OpenIdDict, is there a built-in feature for this?
Please provide guidance on how to configure or extend the ABP framework to achieve this behavior.
Thank you.
ok, I will try and update the result here.
This seems like a drawback for us. Is there any plan to make this configurable through the UI?
Hi @maliming, does it mean there is no UI to configure it and we need to manage the claims in code?
we are using "client_credentials" & "authorization_code" grant types.