You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "krishnamuttevi (via GitHub)" <gi...@apache.org> on 2026/06/01 12:27:35 UTC
[PR] RANGER-5625: User Sync UI fails to render when POST /xusers/ugsync/auditinfo returns invalid "null" strings for syncTime and lastModified [ranger]
krishnamuttevi opened a new pull request, #991:
URL: https://github.com/apache/ranger/pull/991
When invoking the POST /xusers/ugsync/auditinfo API with an empty fileSyncSourceInfo object in the payload, the backend serializes the missing date values as the string literal "null" (e.g., "syncTime": "null") instead of a valid JSON null or omitting the field entirely. While the backend successfully logs the audit, navigating to the UI's "Audits > User Sync" tab and attempting to view the sync details causes the application to crash with an "Oops! Something went wrong..." error.
This indicates an improper backend serialization strategy for empty properties, compounded by a missing frontend fallback or type-check within the "Sync Details" modal component when parsing dates.
This is solved by
1. Changing the data type of time related fields to "date"
2. Update the StringBuilder toString() to handle null value to return current timestamp
3. Rearrange the priority order when multiple syncsource were mentioned (LDAP > UNIX > FILE)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@ranger.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] RANGER-5625: User Sync UI fails to render when POST /xusers/ugsync/auditinfo returns invalid "null" strings for syncTime and lastModified [ranger]
Posted by "pradeepagrawal8184 (via GitHub)" <gi...@apache.org>.
pradeepagrawal8184 merged PR #991:
URL: https://github.com/apache/ranger/pull/991
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@ranger.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org