Skip to content
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

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

Closed
firebird-issue-importer opened this issue Jul 15, 2006 · 10 comments

Comments

@firebird-issue-importer

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-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 16, 2006

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 23, 2007

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-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 23, 2007

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.1 Beta 1 [ 10141 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 19, 2007

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-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 19, 2007

Modified by: @pcisar

Link: This issue is related to QA158 [ QA158 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 19, 2007

Commented by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 19, 2007

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 28, 2008

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 19, 2016

Modified by: @pavel-zotov

QA Status: No test

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 4, 2016

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
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants