-
-
Notifications
You must be signed in to change notification settings - Fork 233
Unable to set FName, MName, LName fields in security to blank [CORE856] #1246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Modified by: @dyemanovassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff To set each name to empty string, simply do not specify it: But there really was a bug when calling services from gsec. And what about IBOADMIN & IBExpert - please contact developers of this programs to make them be able set length of service parameter to 0. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 Beta 1 [ 10141 ] |
Commented by: @pcisar I have verified this with 2.0.1 and my finding are: |
Commented by: @pcisar Fix in GSEC verified for 2.1 Beta 1, test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 11076 ] => Firebird [ 14664 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Done successfully |
Submitted by: Alan McDonald (alanmcd)
Is related to QA158
Once fields FirstName, MiddleName, LastName are set to non blank entries, they cannot be changed to blank entries (i.e. zero length strings).
GSEC does not accept spaces regardless of delimeter attempted: result is the delimeters are used to replace the entries.
Using the Service Manager a space must be used to "blank" out an entry but the entry can never be a zero length string unless the user account is deleted and recreated without the field value being set.
Commits: 4e5adaf
The text was updated successfully, but these errors were encountered: