Github user IsurangaPerera commented on the issue:
    Yes, that's why we have to see it from a different perspective.
    The initial state doesn't change the logic of replaceExisting == true
    But it partially affects replaceExisting == False (This affects only if the 
thread safe problems occur). This means when the issue syncope-1301 occurs 
instead of creating a new token for the same user this will replace the 
existing one (rare situation)


Reply via email to