Hi Engincan, I missed that part in the document. Issue solved. Thank you very much for your support.
Hi, great to hear that, thanks.
Regards.
Hi, I will check and let you know asap.
Regards.
Hi, the encryption of the Client Secret in ABP’s External Provider settings is a security measure designed to protect sensitive authentication credentials. Storing client secrets in plaintext poses a significant security risk, especially if unauthorized users gain access to the database or configuration files. Encrypting them helps prevent exposure in case of data leaks or misconfiguration.
Regards.
Hi, emailing settings are retrieved through the ISettingManager service, which caches data internally. Most likely, the old values you saw were due to cached data.
Now that you've updated the settings again, the cache should be invalidated, allowing the latest values from the database to be used and re-cached. You shouldn’t encounter this issue again.
Regards.
I removed the log out thing, still same issue. I believe that the Identity Module Pro is capturing the user normally but not deleting it.
Hi, there might be a problem as you stated. Our qa team will test this scenario and I'll let you know.
Regards.
Hi, when you update language texts, the changes are made by the host user (tenantId: null). However, these changes are not inherited by other tenants. This behavior is intentional, as it ensures that data remains tenant-specific. Therefore, you need to manually update the text template values for each tenant.
Regards.
Hi, thanks for reporting. We will check this and get back to you.
Regards.
Hello, The thing is that the user is not being deleted. IsDeleted is false and im able to login. To note that when we send the delete request and receive 204 we are performing a logout operation. Do you think that this is causing the issue?
Actually, this shouldn't affect it but it might be. I'll check this scenario.
Hi, When you import a module's source code into your application and use it as a local reference, upgrading it through the ABP CLI only updates the package version—it does not synchronize changes between the two versions. Currently, there is no command available for this purpose.
The best approach is to manually re-install the module by deleting the previous version and adding the updated one in the same directory if there are changes between versions.
Best regards,
Hi, in GDPR module, when you request to delete your account, in the identity pro module an event handler works to delete the user. So, the GDPR module doesn't specifically delete the user rather publish an event to let identity pro to delete the user (soft-delete) and anonymize user data.
So, in your database, the user should be there, but it should be soft deleted in the application and you should be able to see the user's record with IsDeleted field as true.
Regards.
