When using Back-Channel logout, every time a user uses BCL, the audit entry contains all previous trackingIds from past logouts which means every new logout audit entry increases in size. Does the latest session audit entry need to refer to all trackingIds from past destroyed sessions - is this intentional?
- Install AM
- Run the full Postman Collection
- Then run the second part of the collection a few times
- Check the audit logs using something like grep "AM-BACK-CHANNEL-LOGOUT" activity.audit.json and you'll notice the trackingIds array keeps getting added to.