Wt_full_name_too_short constraint failed: check constraint violated: integrity violation: error #1000

Boundary
1

Hello everyone,

We’re seeing a weird error with a specific user when he tries to authenticate via OIDC (Okta) to Boundary. He’s assigned to one group and everyone else in that group manages to authenticate normally.
The error we’re seeing with him specifically is this one:


Apr 30 15:02:43 ip-10-238-238-231.eu-central-1.compute.internal boundary[7104]: {"id":"oOXPYzfAba","source":"https://hashicorp.com/boundary/ip-10-238-238-231.eu-central-1.compute.internal/controller","specversion":"1.0","type":"error","data":{"error":"oidc.(Repository).upsertAccount: db.DoTx: oidc.(Repository).upsertAccount: unable to insert/update auth oidc account: db.Query: wt_full_name_too_short constraint failed: check constraint violated: integrity violation: error #1000","error_fields":{"Code":1000,"Msg":"","Op":"oidc.(Repository).upsertAccount","Wrapped":{"Code":1000,"Msg":"","Op":"db.DoTx","Wrapped":{"Code":1000,"Msg":"unable to insert/update auth oidc account","Op":"oidc.(Repository).upsertAccount","Wrapped":{"Code":1000,"Msg":"","Op":"db.Query","Wrapped":{"Code":1000,"Msg":"wt_full_name_too_short constraint failed","Op":"","Wrapped":{"Code":1000,"Msg":"check constraint violated","Op":"","Wrapped":null}}}}}},"id":"e_SGwpMC3sbB","version":"v0.1","op":"oidc.(Repository).upsertAccount","request_info":{"id":"gtraceid_rinjMJPl2mYudWVsxoxp","method":"POST","path":"/v1/auth-methods/amoidc_XDu6VxhFIQ:authenticate","client_ip":"10.237.80.38"}},"datacontentype":"application/cloudevents","time":"2024-04-30T15:02:43.910117807Z"}

Has anyone seen this before by any chance and could pinpoint what could be the issue?

db.Query: wt_full_name_too_short constraint failed: check constraint violated: integrity violation: error #1000

Thanks in advance

2

Oh, sorry. Also:

Version information:
Build Date: 2023-04-04T15:39:15Z
Git Revision: 482cc6879118f94ce32e28740cf0b4da2507d0aa
Version Number: 0.12.2

3

This is a database constraint on the full name field and would indicate that the full name field for him is empty/ whitespace; can you check to see if that is the case, and if so, set the full name field?

4

Hi @irena.rindos

Thanks for your reply.
His profile looks fine, as this is coming from Okta - his first name and last name have nothing out of the ordinary. Any other ideas?

Thank you

5

For future reference, the problem here was that the displayName in the Okta profile wasn’t populated. firstName + lastName was not enough.