ABP 5.2 Commercial / Blazor Server/ EF / Non-Tiered / Separated Identity Server
Hi, We are planing an upgrade from 5.2 to 7.0 and also migrating to OpenIdDict. We don't currently do any client/application authentication against the ABP APIs from another application. Would there be any effective difference to our end users? We just want to make sure that the following areas wouldn't be affected after the upgrade...
- User names and passwords
- Password complexity settings
- Role and permission setup and assignments
- Two factor setup and functionality
- Account lockout
- Password recovery
- LDAP login
- User/Tenant Impersonation
Thanks in advance!
3 Answer(s)
-
0
There will be no problem with the above functions, you can create a new version of the project to test it.
-
0
There will be no problem with the above functions, you can create a new version of the project to test it.
Great, thank you @mailiming. I also forgot to ask, is there any data that we need to migrate since the schema is changing? I'm also assuming that after the upgrade tests ok, we can just drop the IdentityServer* tables?
-
0
hi
is there any data that we need to migrate since the schema is changing?
You need to correctly create the client you need. Mainly OpenIddictDataSeedContributor
we can just drop the IdentityServer* tables?
Yes, It's always good practice to back up your database though.
