@gterdem
Thanks for your response.
As a digital agency, we run multiple ABP projects, for multiple customers. And those customers (abp-projects), have multiple clients connecting to them. So multiple clients, that connect to our ABP api's.
We did not make all clients, and therefore it is hard to test them. Is there anything that we should report to the developers of the clients? Other than "please test everything".
Are there significant changes that occur, after the migration, that our customers need to report to their clients? Think about endpoint changes. Is there any difference in how tokens are handled?
As far as we know, all clients follow the openid / oauth2 specs. We did not implement custom code on the ABP side.
If this question is hard to answer, I also do like to know. Anything you know of, is desirable to hear.
Is my question to complicated? I know it is a bit abstract. However, knowing any pitfalls would help us a lot. If there is no known pitfall, I do like to know either.
For us it was a combination of
- 1. Development certificate
private void ConfigureOpenIddict()
{
Configure<AbpOpenIddictAspNetCoreOptions>(builder => {
builder.AddDevelopmentEncryptionAndSigningCertificate = false;
});
}
{
...
ConfigureOpenIddict();
...
}
Why not adding this code (maybe with env.IsDevelopment()) to the starter template? This might help a lot of people?
- 2. Setting Loading User Profile to true in IIS
Tnhx for the support!