- ABP Framework version: v8.X
- UI Type: Blazor Server
- Database System: EF Core (SQL Server)
- Tiered (for MVC) or Auth Server Separated (for Angular): yes
We have a legacy system that needs to call an HTTP API within our system, which is built on the ABP.IO framework. Currently, the default authentication method in ABP.IO involves using Client ID/Secret to authenticate the API calls.
However, we want to implement a long-lived token approach for authentication. The idea is to have a hard-coded token in the legacy system, which will be used consistently for making API calls, rather than relying on Client ID/Secret. Is this possible?
Could you please provide me with guidance on how to achieve this long-lived token authentication in the ABP.IO framework? Specifically, I would like to know the recommended approach and any necessary configurations or code modifications that need to be made.
Thanks.
1 Answer(s)
-
0
Hello,
please check similar issue https://support.abp.io/QA/Questions/373/Prolong-token-lifetime-per-each-request if it helps you?
thanks
