There is also a community post from one of the community members: Consume ABP API from Xamarin App. Maybe it can help.
External login automatically registers the user with its entered email. Probably the user with the same email is already registered. You can Customize SignIn Manager or Cusomize Login Page to debug and/or change the default behavior.
The docs I shared is basically for Server-to-Server (Client Credentials flow) interactions. I guess you are already using Authorization Code or Hybrid flow.
The ABP module I posted is running on the Xamarin-Forms application on the user side, because we would like to use the app services (e.g. IProductAppService) directly in the app. Is this possible?
Yes, you can add Applicaton.Contracts and HttpApi.Client layers of your application to your Xamarin app and set your api as remote service so that you can call application service as a remote service (via http calls) directly.
We have a IdentityModel library to automate that process. See auto-discovery configuration section.
Can you watch the webserver memory and check it when it occurs?
We'll create a guide about switching between dynamic and static proxies.
Closing the issue. Feel free to re-open if you come across the same issue.
This is supported by default. You can check Azure Activate Directory Authentication article as a sample. You'll have default login page with external login button you have added at the bottom.
Closing the issue. This will be fixed after version 5.1.3.
I have refunded your question.
Thanks for reporting.
Basically, it is used to sign the tokens.
For development environment, it uses a temporary rsa key (tempkey.rsa) for signing the tokens. You can also use self-signed certificate for development environment as well. For staging or production, you need to use a real certificate (not temp key) to sign the tokens.
For more information, you can check identityserver docs.