Aginity for RedShift is a very popular tool at the company where I work; however, we're working through defining the solution architecture to make RedShift single-sign on possible in our environment. The way this architecture is taking shape, I expect we will need to use a custom driver, as well as to be able to edit/specify the exact ODBC/JDBC string to use to connect using that driver. Under the covers, this custom driver would integrate with Okta & manage Amazon security tokens.
Since the driver that Aginity for RedShift uses is embedded in the tool itself, I have a couple questions:
1) Do you ever plan to support the capability for the user to specify a particular driver for the Aginity for RedShift software to use, including being able to specify the driver connection string?
2) I expect the need for RedShift single-sign capability, with the ability to authenticate against a pre-existing identity store (like Okta) to grow & become a higher priority in the near future; are there any deliverables on the Aginity for RedShift roadmap coming in the near future to help address this?
As it stands right now, our proposed RedShift single sign on architecture would preclude the ability to use the Aginity for RedShift, which isn't desirable; we'd like to see if there is some way forward that would allow our single sign on architecture to work with Aginity for RedShift.
Please sign in to leave a comment.