oracle_user fixes #177
Open
oracle_user fixes #177
Conversation
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
…", support passwords starting with digit or containig special character
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.
Changes summary:
use single quotes for IDENTIFIED BY VALUES
user double quotes for IDENTIFIED BY "plaintext password", allows passwords starting with digit (and other special cases)
upper/lower case for TBS, PROFILE, etc is ignored
wanted/current are stored as a set of tuples:
ALTER USER command is triggered when wanted_set is not subset of current_set
When password hash is provided and is it the same as old password hash, password is not altered. This avoids messing with various security profiles.
port number parameter type is "int"