Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #5678] Authentication lowercase handling causes problem with authkeys #1264

Closed
icinga-migration opened this issue Feb 19, 2014 · 1 comment

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/5678

Created by mfrosch on 2014-02-19 14:45:10 +00:00

Assignee: mfrosch
Status: Resolved (closed on 2014-02-19 15:03:50 +00:00)
Target Version: 1.10.1
Last Update: 2014-02-19 15:03:50 +00:00 (in Redmine)

Icinga Version: 1.10.2
Icinga Web Version: 1.10.0
IDO Version: 1.10.2
OS Version: Debian/jessie
DB Type: PostgreSQL
DB Version: 9.3.2
Browser Version: all

Non-lowercase authkeys don't work at the moment on PGSQL, because authentication can't find the user when it's lowercased.

This should be fixed for general support.

Changesets

2014-02-19 14:45:28 +00:00 by mfrosch 0383b90

Fixed auth_key authentication problems due to lowercase.

This is maily a fix for PostgreSQL, as it causes no problems on MySQL.

The lowercasing enforced in isAvailable won't cause any security problems,
because the auth_key is matched non-case sensitive on the actual login.

Fixes #5678
@icinga-migration
Copy link
Author

Updated by mfrosch on 2014-02-19 15:03:50 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset 0383b90.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant