Hi,
First of all, I apologize for the late reply. I saw your question a long time ago, but due to my busy schedule I didn't have time to test and investigate.
After testing your problem, I saw that this problem was solved in version 4.1.1 of LeptonX. So, it will be enough to update your solution to solve the problem.
Hi,
Unfortunately, we had a short outage yesterday. I'm sorry about that. See: https://status.abp.io/
Is it working when you try it now?
If you asked me this, honestly, the first thing I would ask is:
"How does the existing authentication server actually work? Is there an API? Does it use session cookies? Maybe something like LDAP?"
Because depending on how it works, the way we integrate with ABP will be very different.
If it has an API, we could simply call it to validate users. If it works with session cookies, maybe we can just verify the session and log the user in. If it’s based on LDAP, then we can use LDAP external login provider. And if it only shares a database, it gets tricky — you would have to manually query and trust the user data, which is not ideal.
Also, keep in mind: OAuth2.0 and OpenID Connect are considered the industry standards for authentication and authorization today. If possible, aligning your authentication server with these standards would make future integrations much easier and more secure. See: https://developers.google.com/identity/openid-connect/openid-connect
In short: Without knowing the details, it’s impossible to pick the right integration path.
Let me know more about how it works, and I can suggest a better approach!
Hi,
We have published a tutorial for microservice development, and if you haven't completed this tutorial, I strongly recommend that you do so first. This way you will learn how two microservices will communicate. See: https://abp.io/docs/latest/tutorials/microservice
Many of your questions will already be answered with this tutorial, but you can still ask any questions you have after completing the tutorial ☺️
Hi,
Can you share the logs of your application (log.txt) located under Logs folder to make sure it's a CORS error.
Hello,
Have you configured your gateway according to this change?
If you have configured it, the request should reach the Gateway and be passed to the AuthServer, can you verify this?
Hi,
Can you configure the forward header?
Hello,
ABP Studio checks three conditions for this feature to be active. Please make sure the following conditions are met:
Volo.Abp.Commercial.SuiteTemplates package. If it’s present, you can remove it.appsettings.secrets.json file in the solution. If found, please delete it.Could you please check these and try again?
Sorry for the late reply, by the way. We missed this in our busy schedule.
Hi Martin,
We have reviewed the information you provided, but all the issues are mixed together, which makes it very difficult for us to follow and understand the situation clearly.
To help you more effectively, please create separate questions for each distinct issue. For example, you can create one question for an issue related to ABP Studio and another for a deployment-related problem.
In each question, please include the steps you followed and any relevant logs or error messages. You can also briefly mention what you have already tried, but please note that we need the log records in order to properly identify the root cause of the issue.
This way, we can better understand each issue and provide more accurate and helpful support.
Can you access which folders are under wwwroot/libs folder on the server? If so we can verify if /lodash/lodash.min.js exists. We can also verify if other client-side libraries have been installed.
By the way, I opened an issue to add Blazor Web App to the deployment document. See: https://github.com/abpframework/abp/issues/22654
