Activities of "pierremih"

Even after login that way, the issue is still the same.

I logged in using the swagger's built-in function here

And when checking the Authentication server's page, it does show me as logged in.

We can grant you access to the Github repository. Can you confirm this is you ? https://github.com/berkansasmaz Hangfire is being implemented on branch 346-use-hangfire

I could debug the AbpHangfireAuthorizationFilter class. It is indeed detecting us as not authenticated.

Hi, In-depth debugging of the AbpHangfireAuthorizationFilter seems impossible becaue the .pdb symbols file cannot be found Can you give me indications on how debug AbpHangfireAuthorizationFilter to confirm that CurrentUser.IsAuthenticated is returning false?

We have a related issue. The emailing password is not set on startup or database seeding. We are not using ABP's Settings system but Microsoft's Configuration System and the appsettings.json files, as suggested in ABP's documentation.

• https://docs.abp.io/en/abp/latest/Emailing#email-settings
• https://docs.abp.io/en/abp/latest/Settings
• https://docs.abp.io/en/abp/latest/Configuration

Is there any way to solve this ?

EDIT : The password does not reset on restart. We would like to set it initially using the Configuration system.

Thank you, it seems to have solved the issue.

I understand that this causes issues indeed. We will fix that point. It should resolve many issues we are having.

I granted you access to the repo

We haven't granted you access yet. Can you confirm this is the github account we will give access to ? https://github.com/realLiangshiwei

Sorry for the delay, here are the full steps :

• Have our project running. For that, we would give you access to our github repo which also has the required docker environment required to run it.
• using the "Admin" swagger, call "setting-management/emailing" with POST to define email settings.
• using the "Admin" swagger, call the API "emailing/send-test-email" to try to send an email. It should be working properly.
• using the other swagger, call "setting-management/emailing" with GET to check if the modifications applied there too. It shouldn't.
• using the other swagger, then call "setting-management/emailing" with POST to define email settings there too.
• using the other swagger, call the API "emailing/send-test-email" to try to send an email. It should be working properly.
• using the "Admin" swagger, call the API "emailing/send-test-email" to try to send an email to make sure it's still working. It should be
• Wait between 30 minutes to 1 hour
• using the both swaggers, call both "setting-management/emailing" with GET. One of the passwords got wiped.

If you do not want to reproduce the issue locally, we have a test version running and published. We can grant you access to that. Emails are only sent when using a production environment and a properly set SMTP server, which isn't included in that project.