Hi
We would like to change TOAD theme/color settings when starting new session or reconnecting current one depends on database role.
We want to have different displays if the session is read only or read write.
Is this possible and how?
Best regards
Igor
I think it is only possible with connection colors, but Quest has recently improved that so that the colors are more prominent.
Cheers,
Russ
Thanks for your answer.
We use connection colors, but we want to change them depends on database role that user is granted when connecting to DB to warn user that session is read write or not.
Regards,
Igor
HI Igor,
I'm not clear on what you are asking for. Is this right?
When making a connection, if user has some specific role (I guess you would have to define the role we are looking for), then change the existing connection color if user is connecting read-write, but don't make any change if user is connecting read-only.
There is no way to do that now. The connection color will be remembered once it is set, and the only thing that can change it is you.
In beta, I did just add a system where you can define desired colors for specific databases/users, etc. When making a new connection, you can click "suggest color" and it will pick one based on the rules you define. But also with this feature, once the color is picked for a connection, nothing can change it except you.
-John
Hi John
Yes, that was my question. Why do we need this?
In production DB we have two accounts per developer. One for read only access and second for full. Developer can use color setting to distinguish those two accounts in TOAD. We have two DB roles DEV_RO and DEV_RW for granting and revoking privileges to accounts.
We are planning to use 2FA which allow only one DB account per domain user and my idea is to manage access with granting and revoking right DB role upon developer request with Apex application, which we are using now for locking and unlocking accounts with DEV_RW in production DB.
It will be helpful if we can change/set TOAD color on "New Connection" and much more if we can do it while "Test/Reconnect Session". At the end user is one who can use this or not. We can only help them.
I know, long story... PCI DSS...
I hope the picture is clear now.
Best regards,
Igor
Oh ok. I see. You aren't using Toad's "read only" option, you are controlling this by a role. I thought you were using both. That simplifies things a bit.
But I still have more questions...
Let's say you have a connection defined in Toad with the color green. If this feature were implemented, and user connects, then Toad sees that they have this role, and supposing you want the color for the role to be red. So, we change the color for this connection to red. Ok, fine.
Then the next day they connect again and the role is not there anymore. At this point, I guess you want to color changed back to green? So basically, the presence of the role is like a "color override" without really changing the saved connection color. Yes?
Another question, suppose the user has connections to different databases, but they all have this role. Is it OK if all those connections are the same color?
Hey John,
I REALLY like this idea. We could make good use of it.
Cheers,
Russ
Would a global option like "override connection color with red (or some other color) if role _____ is detected" work, or is this something that you'd like to set on a per-connection basis?
Hi John
We ware patching over the weekend and I did not answer...
Next day color can changed back to default. It is much easier then remember what was the color before "red". And yes, "color override" is what we want.
If user is connected to different DB from same TOAD program, only connections with read write should be "red", read only connections stay default.
We want this to set per-connection as users are connected to several DB from one TOAD and when they switch from one to other DB, it will be fine that user is somehow wart that connection is read write.
Thank you again
Igor
Ok, this will be in the next beta.
Set it up here in Edit Login Record
Or here in the grid:
If you have an override color and role defined, we'll check to see if it's in SESSION_ROLES and adjust connection color accordingly after connection is made, and after your run a SET ROLE command.
Please give it a try next beta and let me know what you think.
Hi John
First, thank you for you very fast response and second, where and when I can download new beta version?
Best regards from Slovenia
Igor
You can get it here.
We release an update almost every monday.
Thanks
I will download it and try next two week and let you know.
Regards,
Igor
Hi John
Today we did first tests and results are great 
My college will do some more to see it there is something unexpected.
We will let you know in January if there is something to add or change.
In the meantime Marry Christmas and Happy New Year to you and your team.
Best regards from Slovenia
Igor
1 Like
Hi John
I try new feature and I noticed that icons in Windows Bar are not grouped any more.
They are shown in order as they were opened. That is not OK.
Second suggestion
I have several open connections at the same database. Then I open new connection to the same database and I change color and press Connect.
Program change color to all connections to this database and not just last new connection (except on Color Override Role - that is great).
Can I have different colors to each connection (on the same database) if I changed them each time?
Best Regards
Tomaz
To group them, check here. I don't think I changed anything with regards to that setting but I can check.
Can I have different colors to each connection (on the same database) if I changed them each time?
No because Toad only keeps one login record for each User@DB (even if you connect with it twice). But there are ways around that. You could either connect as a different user, or make a second TNSNames entry with a different name to the same database. Something like CBAZA and CBAZA_COPY.
Thank you John
Now I can see that this problem is not new. Behavior is the same in official version.
When you have more connections to the same username, windows can be mixed in order as you opened them.
Different users have windows grouped together.
With regards, Tomaz
Ok, ok. Next beta will group them correctly for multiple copies of the same connection.