hi
OpenIddict does not support Front-Channel Logout and Back-Channel Logout mechanisms.
If you only have two clients, system1 and system2, you can override the default LogoutController to return a view and add the logout URLs for both clients.
<!DOCTYPE html>
<html>
<style>iframe{{display:none;width:0;height:0;}}</style>
<body>
<iframe src='https://localhost/signout-oidc'></iframe>
<iframe src='https://localhost/signout-oidc'></iframe>
</body>
</html>
https://github.com/abpframework/abp/blob/rel-7.2/modules/openiddict/src/Volo.Abp.OpenIddict.AspNetCore/Volo/Abp/OpenIddict/Controllers/LogoutController.cs#L12-L24
https://github.com/openiddict/openiddict-core/issues/312
You can maintain an array of client information, and add an iframe for each client to the logout view when logging out from the auth server.
You can check&share all http requests during the logout process.
Use Chrome to record and export as a HAR file.
The HAR file will contain the request and response cookies.
liming.ma@volosoft.com
Thanks.
hi
We will fix this in next studio version.
You can expect to see this option in0.9.20
Try to add template files as EmbeddedResource
<ItemGroup>
<Content Remove="TextTemplates\**" />
<EmbeddedResource Include="TextTemplates\**" />
</ItemGroup>
https://abp.io/docs/latest/framework/infrastructure/virtual-file-system#working-with-the-embedded-files
hi
wwwroot/TextTemplates/TrustInvitationEmailTemplate.html:
Is the wwwroot website a root folder or assets folder?
Please share the csproj file content containing the TrustInvitationEmailTemplate.html file.
hi
Do you have an online website to reproduce?
Thanks.
hi
I will give feedback to the team.
Thanks.
hi
Can you share a GIF to show the problem?
Thanks.
hi
But it was working fine in December before updating Abp Studio.
Yes, we have updated the Studio to the latest version.
Personal License holders can only use the following modules: Account, Audit Logging UI, GDPR, Identity, Language Management, LeptonX PRO, OpenIddict UI and SaaS. Personal License holders cannot use the following modules: Chat, CMS-Kit PRO, File Management, Forms, Payment, Text Template Management, and Twilio SMS.
A non-personal paid license is the standard licensing option for enterprises and commercial entities. Licenses are purchased by the company and can be used by anyone within the organization.
Personal License; on the other hand, is a type of license for private individuals/freelancers/independent developers who purchase licenses with their own funds and solely for their own use. The Personal License has some limitations. In this plan, there can only be 1 developer working on the ABP project and no additional developers are allowed to be added later to the project. Downloading the source-code of PRO modules is not allowed in the personal license plan. There is no microservice template in this plan. There is no tier architecture (Web and HTTP API layers are physically separated) in this plan. Personal License holders can only use the following modules: Account, Audit Logging UI, GDPR, Identity, Language Management, LeptonX PRO, OpenIddict UI and SaaS. Personal License holders cannot use the following modules: Chat, CMS-Kit PRO, File Management, Forms, Payment, Text Template Management, and Twilio SMS. You can access the full module list at abp.io/modules.
