13.0.8.0 - Bug Report: Merge credential list with session setting are ignored & Add-On update window

Hello,

You're absolutely right! Thank you so much for reporting this!

I will open a ticket for our engineers.

Thank you again!

Best regards,

Thank you!

I'm glad to help ;)

Regards,
Min

Hello,

I had a discussion with my team about this and we now have an option for it also in Administration -> Data Source Settings -> Types which is enabled by default;


Could you please make sure it's disabled?

Best regards,

Hi Mark,

thanks, that was it! Now the sessions and credentials are seperated agein! :)

An improvement suggestion: a notice would nice, if you check or unchek the option, that RDM need a restart to apply the setting. ;)

Thanks for your help!

Regards,
Min

Thank you for the suggestion.

Regards

We just upgraded to 13.0.5 and the sessions and credentials were merged (even though a colleague and myself had disabled the option in our settings).

Turns out the global (admin) setting (I didn't even know this settings was available :-)) was set to enable overriding the personal setting (as you describe above).

Was this option on admin set to disabled before (and now it is set by default to enabled?)

Hello,
It's now a setting in the Data source settings to avoid inconsistency in the database. We now recommend to always merge the Credentials and use the Credential List ribbon button instead. By splitting them, you create a possible duplicate folder hierarchy and it could lead to some security mistake. The other workaround is to create your own Credentials folder at the root and change the Sort Order to make sure it's always the last folder.

Regards

If you are going to move this setting into the data source, it should not only be available to Team Data Sources. I could easily setup a SQL Server (or some other Team Data Source) for the Data Source, but why should I have to? Using Dropbox allows me to use the same data source on a home computer as well as a work computer. I understand moving it, but don't penalize people for the data source they have chosen.

Hello,

I will verify with the engineering department if it's possible to make it work with a Dropbox datasource.

As a workaround, you can create an XML database and point it to the "Connection.xml" in your dropbox.

Hello,

We fixed this issue for individual datasources. The changes should be available in the next patch.

Regards

Thank You!!!