Hi
I look to ABP.IO Commercial for next upgrade on our solition based on ANZ because we need some options based on MongoDb. Our solution is not very simple to move in one single step to ABP.IO for this reason I need to invastigate if it's possibile to start some service on ABP.IO and step by step move other.
I check if we can share the same database but I think is not possibile beacuse now the defualt id is GUID and on ANZ is int. So I read the documentation on ABP.IO and, if I correct undestand, I can use ANZ site for autentication and use ABP.IO like a separate service in that way I can share DB or not it's not blocking (my idea / goal could be some microservice that use ANZ solution for autentication)
I terms of license can we have some support during this transition phase (I work on ANZ since ver 0.7)
Any idea o support is appreciated.
Regards
33 Answer(s)
-
0
Hi,
Thanks, I got it now. If you want to call ANZ from ABP.IO, you need to use Token Based Auth if you are going to make requests to get data from ANZ.
You can use this appraoch until you complete the migraiton process. You can create a user for each ABP.IO service and use it this way.
-
0
Hi @ismcagdas
I try some uses case to use ANZ has a Identity for ABP.IO but I think is more complex then migrate user and tenant on ABP.IO.
The problem that I found is that ANZ is older then ABP and Identity soffert of this "distance". For example login page on ANZ is Angular on ABP.IO is part of IdentityServer module, or if I migrate a service to APB.IO I need to share user and permission from 2 different apps. In other words it's a nightmare, opposite migrate user and tenant colud be more simple the "only" impact is related to PK int -> Guid. So if we follow this path user and tenat could be take advantege on the new ABP.IO structure, our migrated module after migration colud be a link on ANZ site and move to ABP.IO using new Identity Server.
So the question is how to change my appsettings.json in ANZ to use ABP.IO has a IdentityServer? We can build a simple guide that can be use for many users in our status.
-
0
Hi @andmattia
In that case, you can just configure OpenIDConnect configuration in your AspNet Zero app's appsettings.json file. If you plan to store all users on ABP.IO database, you may disable the regular login onb your ANZ app and only allow OpenID Connect login.
You are right, both apps (ABP.IO and ANZ) are using different auth approaches and it might be hard to use them together.
-
0
hi can you explain more details about "disable regular login"?
Now I go to test enable openId from ANZ in conjunction with ABP.IO
-
0
I've an issue on IS ABP.IO becasue it not redirect back (opend ticket on ABP.IO).
I've enable OpenId on ANZ
"OpenId": { "IsEnabled": "true", "ClientId": "anz-client", "Authority": "https://localhost:44308", "LoginUrl": "https://localhost:44308/Account/Login", "ValidateIssuer": "false", "ClaimsMapping": [ { "claim": "unique_name", "key": "preferred_username" } ] },
But how can redirect user based on tennat to ABP.IO login page? For ex. :
- app1.demo.com (tenant 1) -> ABP IS with tenant app1
- app2.demo.com (tenant 1) -> ABP IS with tenant app2
I don't want that user need to click OpenId button but I need user go directly to IS when try to login into the app
-
0
Hi @andmattia
Is the IDS URL changing depending on the tenant ? Or is it a fixed URL like app1.demo.com or app2.demo.com ?
-
0
at the moment is fixed but to accomplish our saas model need to be per tenant url *.demo.com (app1 and app2 are tenants)
-
0
I haven't done this before but you may alter the auth server URL here https://github.com/aspnetzero/aspnet-zero-core/blob/dev/aspnet-core/src/MyCompanyName.AbpZeroTemplate.Web.Mvc/Controllers/AccountController.cs#L755