strativd -
Solution
Hello @strativd
When using the api/rest/2.0/auth/token/custom endpoint, user properties such as display name, email, org, and group assignments are not updated with new values — even if the user already exists in the system.
This differs from the api/rest/2.0/auth/token/full endpoint, where — when auto_create is set to TRUE — all user properties are replaced with the values provided in the request. The full token endpoint always overwrites existing user properties.
In contrast, the current behavior of the custom token endpoint is to append certain values (like filter_rules or parameter_values) rather than updating all attributes. Other properties such as display name or groups are not updated through this endpoint as of now.
Going forward, the custom token endpoint will support options to append, replace, or reset user properties, controlled via the persist_option attribute. However, that capability is still under development.
Apologies for the confusion — the reset_option shown earlier in the documentation was a preview of upcoming functionality and should not have been visible until the related changes are ready for production.
For current capabilities, please refer to the official documentation here: https://developers.thoughtspot.com/docs/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fauthentication%2Fget-custom-access-token
When using the api/rest/2.0/auth/token/custom endpoint, user properties such as display name, email, org, and group assignments are not updated with new values — even if the user already exists in the system.
This differs from the api/rest/2.0/auth/token/full endpoint, where — when auto_create is set to TRUE — all user properties are replaced with the values provided in the request. The full token endpoint always overwrites existing user properties.
In contrast, the current behavior of the custom token endpoint is to append certain values (like filter_rules or parameter_values) rather than updating all attributes. Other properties such as display name or groups are not updated through this endpoint as of now.
Going forward, the custom token endpoint will support options to append, replace, or reset user properties, controlled via the persist_option attribute. However, that capability is still under development.
Apologies for the confusion — the reset_option shown earlier in the documentation was a preview of upcoming functionality and should not have been visible until the related changes are ready for production.
For current capabilities, please refer to the official documentation here: https://developers.thoughtspot.com/docs/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fauthentication%2Fget-custom-access-token
ThoughtSpot REST API v2.0 Playground
