feat: support file path for OKTA_PRIVATE_KEY#35
Open
Conversation
Allow OKTA_PRIVATE_KEY to accept either inline PEM content or a path to a PEM file on disk. If the value is a valid file path, the key is read from the file; otherwise, it is used as-is (with escaped newline handling preserved for inline values).
silvexis
force-pushed
the
feat/private-key-file-path-support
branch
from
a966cd5 to
6409ce3
Compare
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
1 participant
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
Allow
OKTA_PRIVATE_KEYto accept either inline PEM content or a path to a PEM file on disk.Changes
auth_manager.py: In__init__, check ifOKTA_PRIVATE_KEYis a valid file path usingos.path.isfile(). If so, read the PEM content from disk. Otherwise, fall back to treating the value as inline PEM (with escaped\nhandling preserved)..env.example: Added documentation noting thatOKTA_PRIVATE_KEYaccepts either a file path or inline PEM content.Behavior
OKTA_PRIVATE_KEYvalue/path/to/key.pem(valid file)\nliterals with real newlines