Activities of "gterdem"
Thank you,
We should put Account related changes migration guide if it is missing.
Please let me know asap once you put all changes related to account module in migration guide as my Application is about to ready for production and I recently upgraded abp version to 5.2.0 due to this issue https://support.abp.io/QA/Questions/2809/httpssupportabpioQAQuestions2558Identity-Server-Error---Microservices
Thank you in advance.
You may have misunderstood that, there are no changes on the Account Module.
The Account Module was hosted by Http.Api.Host application of a tiered (separate identityserver) solution. It has been moved to IdentityServer project. That's all.Okay. So, I will not be able to access through web gateway by adding it into configuration? I have to access those api through Identity server endpoint?
My WebGateway appsettings configuration.
No, you are right. In the microservice template; gateways should be updated. account endpoints should be redirected to AuthServer instead of IdentityService. I have taken note of adding this to the migration guide.
Thank you,
We should put Account related changes migration guide if it is missing.
Please let me know asap once you put all changes related to account module in migration guide as my Application is about to ready for production and I recently upgraded abp version to 5.2.0 due to this issue https://support.abp.io/QA/Questions/2809/httpssupportabpioQAQuestions2558Identity-Server-Error---Microservices
Thank you in advance.
You may have misunderstood that, there are no changes on the Account Module. The Account Module was hosted by Http.Api.Host application of a tiered (separate identityserver) solution. It has been moved to IdentityServer project. That's all.
Thanks for your feedback.
Meanwhile you could update your document for switching the microservice-template to mongodb ab v5.2.
We are also planning to provide some code-base for new microservices by developers to use mongodb.
Good to hear it is working for you.
Closing the issue. Thank you.
Thank you,
We should put Account related changes migration guide if it is missing.
You need to configure front-channel (or back-channel) logout for the external identityserver if you want to sign out from the it as well whenever you logout from abp identityserver.
Abp IdentityServes has this feature implemented. However, you need to manually add it to the external identityserver.
You can check:
- https://docs.identityserver.io/en/latest/topics/signout.html#notifying-clients-that-the-user-has-signed-out
- https://stackoverflow.com/questions/47621453/how-to-enable-front-channel-or-back-channel-logout-in-identityserver4
It seems a nodejs error. When exactly did you get this error? After running tye?
Open the appsettings.json of your project running at 'https://localhost:44362'. Go to the CORS section and add localhost:44308.
Well, it is about external login flow. There is nothing on identityserver about how to redirect back to whichever client is signed in.
I think this should be handled in ANZ project. When redirected back; resolve tenant based on the tenant-id claim you have added and redirect to tenant domain.
Thank you, we have reproduced this problem about multi-tenancy. I have created an internal issue for this. It will be fixed in the next release hopefully.
I have refunded your question credit.