Skip to content

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.

Sign up for GitHub

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

Jump to bottom
Closed
firebird-automations opened this issue Jul 15, 2006 · 10 comments
Closed

Unable to set FName, MName, LName fields in security to blank [CORE856] #1246

firebird-automations opened this issue Jul 15, 2006 · 10 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 1.5.3 affect-version: 2.0 RC3 component: gsec component: security fix-version: 2.1 Beta 1 priority: major qa: done successfully type: bug

Comments

@firebird-automations
Copy link
Collaborator

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
@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

To set each name to empty string, simply do not specify it:
gsec -mod user -fname -mname -lname

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.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 Beta 1 [ 10141 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

I have verified this with 2.0.1 and my finding are:
- It's really not possible to blank these fields in GSEC. Using gsec -mod user -fname -mname -lname as Alex suggests does nothing.
- It works via services API. I have used KInterbasDB that correctly handles empty strings to clear these fields. So the problem is in connectivity components used to call services API, not in services API itself.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue is related to QA158 [ QA158 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Fix in GSEC verified for 2.1 Beta 1, test added.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11076 ] => Firebird [ 14664 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Done successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 1.5.3 affect-version: 2.0 RC3 component: gsec component: security fix-version: 2.1 Beta 1 priority: major qa: done successfully type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexPeshkoff @firebird-automations