1Password : Domain field

Hello,

Unfortunately, this cannot be achieved with a single 1Password entry within RDM.
I will get in touch with our engineering department in order to see if anything can be done on that matter.

I will notify you as soon as I have any update on that matter.


Best regards,

Has there been any movement on this? I use 1Password and RDM and would like a way to specify the domain also.

Nope ..

1Password is (and some could say always been) a 'personal' password manager.
So the concept of 'domain' to them is kinda alien, and they've never really moved into the business area of things.

Devolutions have started to roll out their own 'Password' series of products for business users (taking on things like CyberArk).

Therefore, I don't expect to see either one of them getting together to sort this mess out.

Me, I am just a small time consultant using RDM, and I find having something like 1Password useful; and end up working around the quirks.
I have two entries for AD passwords, one with domain; and one without. And I attach the Credential item appropriately.

I've used a number of password management tools in the enterprise space and most of them (outside of automation/auditing) are pretty average at best. They focus on more storing a password and managing how people access it and track it with auditing, and seem to forget that there is more to it than just a password now. 1Password is one of the few that deals with 2FA/OTP in a team environment. I've now tried eight or so password managers, and not one has dealt with this. Granted this is probably very MSP specific, but even so. Being able to access my mums 2FA token to remotely fix things has been hugely useful. But this is very much off topic.

I don't see why Devolutions can't reference other fields in the 1Password entry, if they can access the password content surely it's as basic as "we look for a field called domain".

@ross01,

Where is the domain saved exactly in your 1Password entry?

Could you post some screenshots of the entire scenario so that I can have a look at it and see if we can do something or not.

Best regards,

Hi,

Just to update this.

I was playing around with 1Password, and it allows you to create a custom field in your entry.

So .. you could in theory create a field called 'Domain', and then enter in the Windows Domain to that field.

Now, looking at your 'Microsoft RDP' (which is essentially the main place people will use this) session type, if you manually enter the details (and not use a Credential stored) "Domain" is one of the fields.

Therefore, when you guys read the 1Password item in the Credential type; can you pull a custom field ?
And can we pass that to the RDP session as the DOMAIN field ?

Like I mentioned, there are plenty of things that use your DOMAIN user without the DOMAIN in the username.
And while most of those won't mind if you pass it anyways, some (like Cisco ASA AnyConnect) will refuse; probably as it has no clue about the domain.

Thanks

I will ask our dev about the custom field in 1Password and let you know the result.

Regards

Thanks ..

From what I see, you can create as many 'custom' fields as you like.

So I am taking a wild guess that they're probably using something like JSON, YAML or XML in the background.

Therefore it should not be a big stretch to accept it, and I don't care if I have to have it a specific way for RDM to parse.

Hello,

We've added a new "domain search field" box in 1Password (web). You will need to enter the field you want to use for the domain. If your field in 1Password is called "domain", then entering "domain" should work.

This will be available in RDM 2019.1.37.0.

Regards,