Announcement

Collapse
No announcement yet.

V 7.00.0003 security module logged database

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • V 7.00.0003 security module logged database

    1.)
    if a User is still in the table sec_logged, by any reason, that user cannot login until he is manually deleted from that table. Even the code from app_login:

    if(sc_logged({login})):
    sc_log_add('login', {lang_login_ok} .": ". [usr_login]);
    sc_user_logout('logged_user', 'logout', 'app_Login');
    sc_redir('Javea');
    endif;
    in which I understand :
    sc_user_logout('logged_user', 'logout', 'app_Login');
    shall logout that user does not work.

    How did it happened?

    programming enviroment->open 1st app->run->login
    programming enviroment->open 2nd app and run, without logout of the 1st app
    programming enviroment->open 1st app->run->login will not allow that user to login

    I am not sure how that might happen on a production-server, but better to put an eye on that.


    2.)
    which I have seen, there are some hours time differece between table sec_logged and the table sc_log
    Last edited by EricB; 02-24-2013, 06:50 AM.

  • #2
    Hello Eric,

    I will contact our bugs team regarding this issue.

    regards,
    Bernhard Bernsmann

    Comment


    • #3
      yes same problem please fix it!!

      I'm have the same problem with login user's

      Comment

      Working...
      X