This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 43%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
This document describes steps to select user attributes to appear in claims token:
You should now see ShoeSize in the list of attributes collected during the sign-up journey, and see it in the token sent back to your application.
After following above steps custom attributes do not appear in the token sent back to my application. What am I doing wrong?
Hi, I followed the same guide and was able to get the correct shoe size token. I would run through the process one more time. There could have been a bug where it didn't populate properly. If it still doesn't work I will escalate this for you.
Best,
James
The problem was that the properties were not populated with values. Apparently if a value is null it is not returned. Seems an odd behavior given that many other (unrelated) properties on the response object are null, empty, or undefined.
