Hi clahey
Is Redis active in your project? Try clearing your Redis. If this doesn’t solve the issue, could you please send your project to [email protected] so that we can reproduce the issue on our end?
Hi
Have you also added the logout URL?
After adding the logout url, add the Redirect URIs to the domain http version you added.
Example:
http://your-domain.com
If you still receive the same error as a result of these steps, you can share your project to [email protected] e-mail address.
Hi
Here, you need to correct the ForceLogout operation so that it can be used by the UserAppService and the TokenAuthController, as it will be in common use. You can take this approach instead of sending a request to TokenAuthController through the AppService method.
Hi
If you are using domain in Redirect URIs, can you test again without specifying a port?
Hi
After clicking Add a platform, Configure platforms opens on the right. You need to select the Single-page applications field. You can add this value "https://your-domain:4200/" to the Redirect URIs section. After adding it, it will appear in the screenshot below.
Hi
To do this, log in to the Azure Portal and navigate to Azure Active Directory > App registrations. Select your application, go to the Authentication tab, and add the required redirect URI under the Redirect URIs section. For example, you might add a URI like https://yourdomain.com/signin-oidc. Make sure the URI matches your application’s setup, taking into account whether it’s a development or production environment. You can use the Quick Start feature on Azure, which allows you to automatically select Redirect URIs by selecting your application type.
Hi hongbing.wang
Can you share with us how you call the AppService method in TokenAuthController? When you put a breakpoint in the app service method in debug mode, does it go into the AppService method?
Hi rickfrankel
Thank you for your feedback. We have created an issue regarding the Redis usage increase problem. You can follow the changes here.
Hi rickfrankel
To find the exact cause of this performance issue, is one of the Social Login integrations active under Authentication in appsettings.json in your application? Is the AllowSocialLoginSettingsPerTenant setting also set to true?
Hi
Thank you for the update! I’m glad it’s working now. Please keep monitoring and don’t hesitate to let us know if you encounter any further issues.
