Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.

Explicit domain credential mapping to an endpoint for injection

Customers are requesting the ability to map a domain type credential to an endpoint so that it is the only domain credential made available for injection when accessing an endpoint through Bomgar PA.

  • Guest
  • Apr 3 2018
  • Future consideration
  • Attach files
  • Guest commented
    31 Jan, 2020 09:10am

    AFAIC, this is a fundamental shortfall.

    The desired behaviour would be that only the related credentials would be listed, rather than the full list of those that the operator has permission to inject.

    To my mind, a sensible logic function should be added at the point of processing / creating the dropdown list to show only matching credentials where the domain suffix (i.e. the string before the '\' delimiter) in the credential matches the domain on the target machine.

    This logic would only work against domain devices, but would provide a significant reduction in the visible noise when there are thousands of listed credentials, many very similar.

    Given this, the easiest approach (and surely the easiest to implement) would be to display the credential Comment attribute instead of the username;

    - Import a credential (domainA\user) with a password comment of "Business A Admin"
    - Import a credential (domainB\user) with a password comment of "Business B Admin"

    The backend functions / links to objects themselves should not need to be addressed, but when the injection list is rendered it displays the associated comments ("Business A Admin" and "Business B Admin") instead of the credential itself.

    Where there is no password comment; display the credential. This change would allow existing instances who don't have the comment attribute defined to continue as they are working, but would allow estates such as ours the ability to easily see the appropriate credentials to be utilised.

    ...Of course if a filter was added to this as well, the solution would be absolutely perfect.

  • Guest commented
    10 Apr, 2019 08:58pm

    I would like to see that as well.  Basically it wouldn't prompt you for a credential, it would just log you in with a pre-determined injected credential.