Hi, I’m experiencing issues with user provisioning...
# troubleshoot
l
Hi, I’m experiencing issues with user provisioning functionality in GMS. Having successfully set up OIDC authentication in our system I see most users being able to login successfully and use the DataHub UI. As it comes, I’m the unfortunate exception with my first name containing a localised character. The information passed from the authenticator to Datahub doesn’t allow the latter to provision my user and grant me a URN. These are the symptoms: UI shows
Copy code
Failed to perform post authentication steps. Error message: Failed to provision user with urn
Frontend throws the following exception:
Copy code
Caused by: com.linkedin.r2.message.rest.RestException: Received error 500 from server for URI <http://datahub-datahub-gms:8080/entities>
The gms application complains:
Copy code
Caused by: java.sql.SQLException: Incorrect string value: '\xC5\x82aw F...' for column 'metadata' at row 1
Obviously, UTF-8 “ł” character handling issue. What can be done in this situation? And no…, I’m not that much into changing my name, Jaros*ł*aw is not that bad ;) Thanks in advance for your suggestions!
a
Hi @lively-spring-5482, what version of GMS are you on?
l
Copy code
datahub-gms:
  enabled: true
  image:
    repository: linkedin/datahub-gms
    tag: "v0.9.6.1"
That is the current version. We’ve been updating the installation a couple of times however, starting from as low as 0.8.2x
@astonishing-answer-96712
a
Ok, I think @echoing-airport-49548should be able to help you with OIDC issues here
e
Hey @lively-spring-5482 sorry you’re dealing with this issue
l
Hey, no worries 🙂
e
Looks like we may not be encoding urns/names that have localized characters correctly here
Do you have a stack trace that gives some line numbers?
Are you seeing any errors on the frontend pod too?
That would also be useful
l
That would be the GMS stack trace
Looking for the front end
That is the front end stack trace
e
Thanks this is helpful! I’ll take a look into what’s going on here
l
thanks!
m
Hi there, any solution to this? I am a having a UTF-8 encoding issue too - see here: https://datahubspace.slack.com/archives/C029A3M079U/p1695360161393249