Location By IP Range Wizard - 8.2

(imported topic written by cstoneba)

I’m running 8.2.1079 and am logged in with an LDAP MO account. I try to run the Location By IP Range Wizard, but when I click on “Finish” in the wizard, I get the attached screenshot saying on Master Operators can complete this action.

(imported comment written by cstoneba)

anyone?

(imported comment written by JasonHonda)

Do you mean the Location Property Wizard in BESSupport? Does the operator have the permission to create custom content?

(imported comment written by cstoneba)

Yes, that wizard. The operator is a Master Operator and it still gives that message.

(imported comment written by JasonHonda)

The console generated this error when the Wizard tried to create a new property it appears.

Can you go to Tools -> Manage Properties and create a new property there? Are other operators affected by this?

Things work fine for me in 8.2 but I’m not using LDAP.

(imported comment written by cstoneba)

Yes, I can create a new managed property. I can run the wizard with my local MO account, but not with this LDAP one. I’ll have to see if other LDAP MO get this same message.

(imported comment written by cstoneba)

Got it figured out. For some reason, I had to grant my LDAP user account in the console Explicit MO Permissions, Effective Permissions wasn’t enough apparantly. Operators > ldap account > Details Tab > Permissions > Explicit Permissions - Master Operator = Yes, Custom Content = YES

(imported comment written by JasonHonda)

Awesome. Just had filed a bug so that we could test this out more but it looks like I can call that off.

(imported comment written by JasonHonda)

Looks like there was a bug hidden here. From what I am told, you shouldn’t have had to set the explicit permissions, and effective should have been enough for this to work. That will get sorted out I’m sure in some yet to be determined future release of the console.

(imported comment written by cstoneba)

thanks JasonHonda. When you get the bug#, can you post it?

(imported comment written by JasonHonda)

Sure bug # is 46884 in case you want to reference it when talking with support.