The problem has been resolved. I found a clue to the solution in note 1687748.
According to the note the issue occurs with Secure Login Library 1.0 with low support stack. I was using Secure Login Library 2.0 SP 0.
I had updated Secure Login Library to SP2 and the issue was resolved.
Secure Login Library 2.0 should be added to the affected releases of note 1687748.
Best Regards,
Ilia Medvedev.