Pivotal SSO 1.16.16
This is an issue exposed in the UAA component. The edge case leading to failure occurs when there is a 'null' value for a key in the client registration, specifically the additionalInformation section.
The workaround for now is to update the clients that have null values on some keys using the regular "/oauth/clients" (instead of "/oauth/clients/tx") endpoint.
A fix for this should be released in TAS Elastic Application Runtime 6.0.25