DEV Community

yutianle
yutianle

Posted on

LinOTP title matches identify an OTP control plane with two separate identity paths

LinOTP title matches identify an OTP control plane with two separate identity paths

LinOTP provides one-time-password validation and token administration. It exposes a user self-service path and an administrative path that can manage tokens, realms, policies, and identity resolvers. Those paths have different audiences and different credential requirements. A public title match can identify a candidate, but a real review starts with the administrative realm and the authentication flow behind it.

A count-only ZoomEye query on November 18, 2026 returned 595 matches for title="LinOTP" and zero for app="LinOTP". The search used sub_type=all, page 1, and pagesize 1. The title matches could include login pages, documentation, and references that are not live LinOTP servers. The zero app result shows that an application fingerprint is not guaranteed even when the title is visible.

LinOTP documentation describes separate user and administrator paths. The self-service interface uses the user-service API against a configured identity resolver. Administrative interfaces such as /admin, /system, and /manage are protected by an administrator realm and session handling. Current documentation states that LinOTP 3 checks authorization for the administrative API itself rather than relying only on web-server basic authentication.

Inventory the two paths

Map each LinOTP server, version, web endpoint, and network path. Record the realms and the user ID resolvers behind them. Identify which identities belong to the administrator realm and how they authenticate. Review token assignment, resynchronization, PIN policy, and emergency access. A user who can validate an OTP is not automatically a user who can manage tokens or change realm membership.

Review the administrative session. The documentation describes an admin_session cookie and session parameter for management API requests. Check session lifetime, cookie flags, TLS termination, and logout behavior. Test that a user-service session cannot call administrative endpoints. Test that an administrator from one realm cannot manage another realm unless the policy explicitly grants that authority. Use non-production accounts for the boundary tests and preserve the responses as evidence.

Protect the OTP role

An OTP server is part of the authentication path for other systems. Availability and integrity therefore matter even when the server is not internet-facing. Restrict the administrative interface to a management network, separate it from the validation endpoint, and require strong authentication for the administrator realm. Monitor changes to realms, resolvers, token assignments, policies, and administrator accounts.

Check integration credentials and the systems that trust LinOTP responses. A compromised OTP control plane may be able to change token state, reset a factor, or alter the policy that decides which factor is required. Review those downstream trust relationships with the application owners. Preserve audit logs and configuration before removing a suspicious administrator or token.

The 595 title matches are a candidate queue, not a confirmed list of OTP servers. Verify the product and version from an authorized source, map the admin realm, and confirm the self-service boundary. The small application fingerprint count reinforces why a single field cannot carry the inventory. The useful result is a tested identity map for each real deployment.

References

Top comments (0)