Hi Felix,
while it still would be nice to have some kind of "debug mode", I've figured out something. It looks like there is something with the "Path" object. Look at this example:
{
"Objects": [
{
"Type": "Credential",
"Path":"/Folder1/Folder2/Folder3/Folder4/Sample",
"Name":"Entry1",
"Username":"administrador",
"Password":"password"
},
{
"Type": "Credential",
"Path":"/Folder1/Folder2/Folder3/Sample",
"Name":"Entry2",
"Username":"user",
"Password":"password"
}
]
}
This RoyalJSON should create a folder named "Sample" under "Folder4" and another one under "Folder3", right? Well, it doesn't. It creates folder "Sample" under "Folder4" and puts both entries into it.
Instead, this one works as expected:
{
"Objects": [
{
"Type": "Credential",
"Path":"/Folder1/Folder2/Folder3/Sample",
"Name":"Entry2",
"Username":"user",
"Password":"password"
},
{
"Type": "Credential",
"Path":"/Folder1/Folder2/Folder3/Folder4/Sample",
"Name":"Entry1",
"Username":"administrador",
"Password":"password"
}
]
}
Regards,
Matteo
Hi Felix,
glad to help :)
Yeah, I've read about the the dark side... I mean, the hard method ;), but since our password manager exports the passwords in a format that's really similar to "The easy (less flexible) method" format, it's much much simpler to me to use that method. So, I think I'll wait for the next beta, thanks.
One last question: speed. I've noticed that my script takes like 4 seconds for generating the RoyalJSON output, and RoyalTSX takes it's time to format everything, something like 30 passwords/sec. Since we have thousands of credentials, it takes some minutes each time I reload it. Is this something that you also are experiencing?
Thanks again for your kindness and for making this product better and better.
Regards,
Matteo
Hi Madan,
we're currently in the process of developing an import/export system for dynamic folders.
When that's complete, we'll be able to share some samples.
cheers,
felix
Hi Matteo,
well, all the parsing and general magic in RoyalJSON surely introduces performance penalties.
You might want to think about switching to Dynamic Credentials and don't import any passwords in the dynamic folder script. This way we don't have to encrypt all those passwords while loading the dynamic folder's contents but only when requested by a connection.
There's a dedicated section about Dynamic Credentials in the documentation. Please let me know if that helps!
cheers,
felix
Hi Felix,
thanks for your support.
I've read about Dynamic Credentials (really nice feature!), but that's not a viable option for us since we often work without direct internet access.
Thanks again, have a nice day!
Matteo
Hi there,
I'm happy to report that Royal TSX 4.0 has been released and includes this feature.
For more information about the major new features of Royal TSX 4.0, please head over to our major upgrade landing page.
cheers,
felix
Hi Felix,
Checking if there is any update on the development of the API for connectivity that could be used to connect to other privileged management vaults. Appreciate any update you might have on estimated availability.
Hi Matt,
we're in the middle of the implementation phase. We already have prototypes running that can connect to and retrieve credentials from Secret Server and Pleasant Password. So it's looking pretty good. We still can't provide an ETA for the first public beta though.
cheers,
felix
Yes, this will be generic and work for all kinds of external data sources.
Daniel Staal
Royal TSX integrates with some password stores, but none of the current ones are really enterprise-ready password storage. It would be nice to offer integration to one (my employer uses Pleasant Password.), or ideally an API to enable shims to be written between the API of the password storage and Royal TSX.
I'm posting this in Mac as I'm a Mac user, but I know both pieces of software exist on other platforms, so really this should be considered a general feature request.
2 people like this idea