+ New Ticket

How to setup a new connection without saving password in Aginity Pro?

Comments

4 comments

  • Official comment
    Avatar
    George L'Heureux

    Hi Daniel,

    I'm George, one of Aginity's product managers. Thanks for writing!

    You're correct that currently we require the password to be saved in the connection when you construct it in Aginity Pro. It's not a bug; however, I want to capture your feedback as an opportunity for additional functionality within Pro. Perhaps you could help me.

    I'd be interested in understanding what your desired experience would be. Since Pro supports multiple platforms and connections simultaneously, would you want to:

    • Enter a password for a connection upon your first exploration of it following application launch (that is, when you click into Database Explorer or attempt to submit a query against it)?
    • Enter a password immediately upon launch for any connections that don't have passwords saved?
    • Enter a password every time you want to run a query?
    • Enter a password every X hours?
    • Some other usage pattern?

    I'm interested in understanding how you'd like to see the tool work. Looking forward to your thoughts.

    Best

    George

    Comment actions Permalink
  • Avatar
    Daniel

    Hi George and thank you for your input.

    I would say option 2 would suit me best, also most similar to what experience we are used to from Aginity Workbench from before? If you would like to save a password, e.g. in a test environment, this can be proivided with a checkbox or similar?

    We are currently testing Aginity Pro and comparing it to Workbench, I would like an option that would provide the smoothest transition for existing Workbench users, in addition stay compliant with our internal IT security policy.

    0
    Comment actions Permalink
  • Avatar
    Daniel

    Also on the same note since you mention multiple connections and platform support:

    • I think auto-login upon startup on should be a selective and not a mandatory option, and you should also include a disconnect feature. I am a big user of e.g. SQL Developer from Oracle and DBeaver, both support cross platform OS + database connectivity through jdbc drivers. I often connect to the databases I currently work on, and disconnect when I am done working with those. When working across various environments: dev, test, qa production and more this is essential to me, to keep things separate depending on my needed tasks.
    • Not demanding password to be saved in a profile will solve part of this issue, but disconnect option should also be added.
    0
    Comment actions Permalink
  • Avatar
    George L'Heureux

    Daniel,

    Thanks for your input! I've created a ticket to track this request, and will discuss this feature opportunity with our team this week.

    We look forward to your additional input - thanks for being a part of our community!

    George

    0
    Comment actions Permalink

Please sign in to leave a comment.