Skip to main content
Planned for development

Using OAuth2/OpenID authentication with DB extractor.

Related products:Extractors
  • October 21, 2024
  • 3 replies
  • 30 views
  • Sachin Perera

Elkem ASA is no longer going to use pure SQL due to a risk SQL poses. They want to use OpenID/OAuth authentication against DB extractor for this reason.

As per my knowledge, we currently don’t have the option to use OAuth2/OpenID authentication with DB extractor.

3 replies

Forum|alt.badge.img

Hi Sachin,

We have registered a similar request for a different customer and are evaluating including where and how this functionality fits in our longer term roadmap.

The complexity of this request is a little bit greater than “simply” adding OAuth2/OpenID support to the DB extractor (we would preferably do it for all python based extractors in one go), so it will require more development and testing than “just” for the DB extractor. Due to our ongoing workload and product plans, barring any unexpected available capacity, this is not likely to happen until sometime towards the end of 1st half, 2025.


Forum|alt.badge.img

@Sachin Perera - What DB and communication protocol are they talking about here?

 

Our ability to support different authentication options are highly dependent on the underlying connection protocols. ODBC has it’s set, direct to Snowflake has a different set, etc, etc. 


Forum|alt.badge.img
  • Elkem
  • 3 replies
  • October 24, 2024

Hi! Elkem ASA has found another solution and is in the process implementing it. This case is no long relevant for Elkem. Thanks for now. :)


Reply


Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings