Hi,
no such document,
I suggest you use the account module's page instead of your own. you can customize pages. This way, you can get the benefits of ABP; we will add new features and bug fixes to the module in each version.
Hi,
I checked again, and the AuthenticatorAppComponent
is not a declaration component, so you can't use it.
what's your email , i can share the component code with you
Hi
I’m not mean the source code, it is a part of account module, since you are the team license, you can’t get the source code.
But you can use it as NPM package reference. Just import the component and use it.
The NPM name is @volo/abp.ng.account
hi
You can check this https://abp.io/qa/questions/8242/3a163c3f-da3c-3082-dd17-d659406974a1
Hi,
okay, i see, you include the source code to your project.
you need to download the new source code to compare it, and copy to your project.
Hi,
You can try to generate a new credential https://abp.io/docs/latest/solution-templates/layered-web-application/deployment/openiddict-deployment#signing-and-encryption-certificate
In the production environment, you need to use a production signing certificate. ABP Framework sets up signing and encryption certificates in your application and expects an openiddict.pfx
file in your application.
This certificate is already generated by ABP CLI, so most of the time you don't need to generate it yourself. However, if you need to generate a certificate, you can use the following command:
dotnet dev-certs https -v -ep openiddict.pfx -p ace85f4f-9e64-48a5-8d8e-9e630f44c944
ace85f4f-9e64-48a5-8d8e-9e630f44c944
is the password of the certificate, you can change it to any password you want.
It is recommended to use two RSA certificates, distinct from the certificate(s) used for HTTPS: one for encryption, one for signing.
For more information, please refer to: https://documentation.openiddict.com/configuration/encryption-and-signing-credentials.html#registering-a-certificate-recommended-for-production-ready-scenarios