Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #2142] AD LDAP user import fails #599

Closed
icinga-migration opened this issue Dec 3, 2011 · 9 comments
Closed

[dev.icinga.com #2142] AD LDAP user import fails #599

icinga-migration opened this issue Dec 3, 2011 · 9 comments
Labels
bug
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Dec 3, 2011

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

Created by fungus on 2011-12-03 01:42:42 +00:00

Assignee: (none)
Status: Resolved (closed on 2011-12-09 10:44:22 +00:00)
Target Version: 1.6.1
Last Update: 2011-12-14 21:29:08 +00:00 (in Redmine)


New installation of Icinga-web 1.6

Attempts to logon as a new user fail with:

Uncaught Doctrine_Record_UnknownPropertyException thrown:
Unknown record property / related component "NsmPrincipal" on "NsmUser"

Authentication works fine with the internal provider. No new database records were created up to this point.

I attached the debug log which isn't very helpful.
Also attached the stacktrace that got returned for the login POST.
Also attached the additions to the authentication config.

The point in the code where it fails is in file:
app/modules/AppKit/models/Auth/DispatchModel.class.php
In function importUser:

This fragment fails:
$padmin->updatePrincipalValueData(
$user->NsmPrincipal,
array(),
array()
);

Attachments

Changesets

2011-12-09 10:35:03 +00:00 by mhein 757e604

* Fixed AuthDispatcher (fixes #2142)
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 3, 2011

Updated by chodorenko on 2011-12-03 23:12:31 +00:00

Please read Update Manual
Update Database

INSERT INTO nsm_target (target_id,target_name,target_description,target_class,target_type) VALUES ('19','IcingaCommandRestrictions','Disable critical commands for this user','IcingaDataCommandRestrictionPrincipalTarget','icinga');

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 5, 2011

Updated by fungus on 2011-12-05 16:27:09 +00:00

  • File added nsm_target.sql

Thanks for looking.

This wasn't an upgrade, fresh install. Also the suggested record already exists. See dump of said table.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 7, 2011

Updated by gpduck on 2011-12-07 02:58:34 +00:00

This is caused by the changes in root/app/modules/AppKit/lib/database/models/generated/BaseNsmUser.php introduced in revision 01bf9d7, specifically line 167 that renamed NsmPrincipal to principals (which was then later renamed principal in 819ab0f).

This can be fixed by editing line 293 in root/app/modules/AppKit/models/Auth/DispatchModel.class.php to say:

$user->principal,

instead of $user->NsmPrincipal

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 7, 2011

Updated by fungus on 2011-12-07 19:00:03 +00:00

Yay, thank you very much. That is exactly the fix. Works perfectly.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 9, 2011

Updated by mhein on 2011-12-09 10:44:22 +00:00

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

Applied in changeset 757e604.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 14, 2011

Updated by netscraper on 2011-12-14 20:59:17 +00:00

gpduck wrote:

This is caused by the changes in root/app/modules/AppKit/lib/database/models/generated/BaseNsmUser.php introduced in revision 01bf9d7, specifically line 167 that renamed NsmPrincipal to principals (which was then later renamed principal in 819ab0f).

This can be fixed by editing line 293 in root/app/modules/AppKit/models/Auth/DispatchModel.class.php to say:

$user->principal,

instead of $user->NsmPrincipal

Here works this fix also. I've been looking for a solution while 3 hours. many thanks for your support! Why the fix has not yet entered in the current package?

regards from switzerland

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 14, 2011

Updated by mfriedrich on 2011-12-14 21:00:57 +00:00

  • Target Version set to 1.6.1

because another release on the 1.6.x tree is needed to let the fix hit upstream.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 14, 2011

Updated by netscraper on 2011-12-14 21:14:00 +00:00

dnsmichi wrote:

because another release on the 1.6.x tree is needed to let the fix hit upstream.

Ok, nice. Thanks for your commitment!

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Dec 14, 2011

Updated by mfriedrich on 2011-12-14 21:29:08 +00:00

dunno when it will happen though - minor bugfix releases are up to the respective release managers for their packages (marius for the web).

@icinga-migration icinga-migration added this to the 1.6.1 milestone Jan 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.