We have the following description for these 2 attributes in the docs:
Modified Timestamp Attribute Name
The identity Data Store attribute used to return modified timestamp values.
amster attribute: modifiedTimestampAttribute
Created Timestamp Attribute Name
The identity Data Store attribute used to return created timestamp values.
amster attribute: createdTimestampAttribute
the same description is in the explanation text in the XUI.
It would be good to add that:
- both are read by the "updated_at" claim
- This is only mentioned in the OP for Mobile Connect doc:
The updated_at values are read from the profile attributes you specify. When using DS as an identity data store, the value is read from the modifyTimestamp attribute, or the createTimestamp attribute for a profile that has never been modified.It doesn't stop you though from enabling them in other configurations.
- You either leave them both unset or you set them both, if you set only one leaving the other blank then access_token is failing with 500 error.
These attributes are set by default when we configure the OP for Mobile Connect, otherwise they are not set. But you can use them in any flow. It's good to mention they are going as a 'pair'.