NetXMS Support Forum

English Support => General Support => Topic started by: pvo on April 15, 2020, 11:48:52 PM

Title: Cannot get web service definitions: Access denied
Post by: pvo on April 15, 2020, 11:48:52 PM
When I open Configuration - Web Service Definitions in the Web Management Console or in the Windows Management Console I get following error message: "Cannot get web service definitions: Access denied".
What does this error mean?
Title: Re: Cannot get web service definitions: Access denied
Post by: Victor Kirhenshtein on April 16, 2020, 08:56:15 PM
Hi,

make sure that your user has system access right "manage web service definitions".

Best regards,
Victor
Title: Re: Cannot get web service definitions: Access denied
Post by: pvo on April 16, 2020, 09:09:32 PM
I was logged in as admin, but the Admins group didn't have the "Manage web service definitions". It works now, thank you for your help.

I didn't modify the Groups rights therefore it is probably default setting. It is strange. I thought that the Admin group has all rights. Why is this right an exception?
If there is difference in database initialization and for other databases is it OK. I use the PostgreSQL database.
Title: Re: Cannot get web service definitions: Access denied
Post by: Victor Kirhenshtein on April 18, 2020, 03:19:12 PM
It could be bug in upgrade procedure. This is new access right introduced in version 3.2, so if you have upgraded from older version it may not have been added by database upgrade tool.

Best regards,
Victor
Title: Re: Cannot get web service definitions: Access denied
Post by: pvo on April 18, 2020, 04:19:05 PM
It was fresh 3.2. installation and I've used Debian Buster packages therefore I'm not sure about the exact version but I guess it was 3.2.400.
Title: Re: Cannot get web service definitions: Access denied
Post by: pvo on April 19, 2020, 03:29:35 PM
I've tried a new fresh installation with the latest Debian packages 3.2.472 and the rights are OK.
Title: Re: Cannot get web service definitions: Access denied
Post by: Victor Kirhenshtein on April 20, 2020, 10:40:06 AM
Just checked - there was a fix in DB init script between 3.2.400 and 3.2.472 for exactly this issue. Completely forgot about it.

Best regards,
Victor