Add Oracle thick mode support via ORACLE_THICK_MODE env var - #177
Open
Gigituier wants to merge 2 commits into
Open
Add Oracle thick mode support via ORACLE_THICK_MODE env var#177Gigituier wants to merge 2 commits into
Gigituier wants to merge 2 commits into
Conversation
Updated password handling in lambda function to use the correct pending password from the dictionary.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds configurable Oracle Thick mode support to the SecretsManagerRDSOracleRotationSingleUser template.
Changes
Oracle Thick Mode Toggle
Adds module-level initialization that checks the ORACLE_THICK_MODE environment variable. When enabled, calls oracledb.init_oracle_client() before any connection is created. This is required for customers whose Oracle databases enforce Native Network Encryption (NNE), checksumming, or Kerberos authentication, features that only work in python-oracledb's Thick mode.
New environment variables:
When enabled, Oracle Instant Client libraries must be available via LD_LIBRARY_PATH (e.g., via a Lambda Layer).
Backward compatible, default behavior (thin mode) is unchanged.
Testing
Tested against Oracle Database Free (26ai) running on EC2 with Native Network Encryption set to REQUIRED:
Note
The same change should be applied to SecretsManagerRDSOracleRotationMultiUser as well.
Related