Currently, when using the web login user interface to integrate with other services, the client name is fixed to "OpenTera-Web-Client". This causes 2 issues:
- Logs entries for login are not as explicit as they could be (always referring to OpenTera-Web-Client
- An error is generated because "OpenTera-Web-Client" isn't a known client (no entry in the server settings table in the database)
Proposed fix should use the X-Client-Name header when displaying the login view to set the name (defaulting to OpenTera-Web-Client if unspecified) and adding "OpenTera-Web-Client" as a known client by default to prevent error messages in the logs.
Currently, when using the web login user interface to integrate with other services, the client name is fixed to "OpenTera-Web-Client". This causes 2 issues:
Proposed fix should use the X-Client-Name header when displaying the login view to set the name (defaulting to OpenTera-Web-Client if unspecified) and adding "OpenTera-Web-Client" as a known client by default to prevent error messages in the logs.