Authorized app with password credentials – svc_ln

The authorized app can use the standard service account svc_ln. This can be useful, for example, when 20 similar machines must log on using the same service account.

Note:

In this scenario, each machine stores the credentials for the svc_ln service user. All requests—regardless of which machine sends them—are logged as sent by svc_ln. Consequently, you cannot see in LN or in the log data which machine initiated a request.
By default, this means there is no per-machine traceability or accountability.
If you need traceability and accountability per machine while still using a single service account, assign a unique identity to each machine. To do this, configure API identities, API route authorizations, and identity switching. For details, see the relevant chapters and tutorials in this guide.