*** Bug 1389230 has been marked as a duplicate of this bug. ***

User mapping requirements will certainly have to expand slightly.

One customer requirement is for specific real Satellite users (e.g. innesd, inecas, bbuckingham) to map to a generic local account on the client systems (e.g. TeamOps, TeamAdm etc.).  This specific customer requirement wouldn't require a Satellite user to be mapped to any more than 1 local account, but I can see this being required for other situations.

As for the scenario where the mapping is also dependant on the host or hostgroup, I'm afraid I can't expand further.  Under this specific customer requirement, Satellite users are not given different privileges depending on which client machines they run jobs on.  i.e. an ops user will always map to the Ops local account on every machine that they try to execute remote commands.

Ok, this simplifies the situation a bit.

Hello,

Is there any progress to this RFE?

This has not been triaged to a release.

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.