I have following problems with “Check_MK 1.6.0p7 Managed Services” in distributed monitoring setup.
I created a user for our slave site which should have a read-only access to this slave site.
In Distributed Monitoring configuration for this site I un-checked the option “Disable configuration via WATO on this site”
In User Configuration I checked “Change password at next login or access”.
After user tried to log in to his local site web interface, he was not able to change the temporary password. I had to allow him to change the configuration. This not desired behavior for me. The user should be able to change temporary password or his normal password independently on configuration of the rest of the parameters.
There is one more problem. When the user change his password on slave site, this change is not replicated back to master site and by next configuration synchronization is the password overwritten with original temporary password on master site.
This brings problems and means for me, that anytime the user changes his password I have to manually copy the change to master site.
Well why not provide access through master instance and replicate to the slave ? Then if you have managed edition you can provide access to just a client if you are on raw or ee you can manage the acess and view with rules and contact groups.
Or you want another type of solution ?
Your way works. I have to set the user as Global then I can log into master instance. If I set the user to actual customer then the login does not work.
My point is, that it should function like I described anyway.
I think we can leave this thread as it is for future reference and create a new post under product ideas. That way it will be focused on the feature to vote on.
