From dev-return-16440-archive-asf-public=cust-asf.ponee.io@syncope.apache.org Tue Oct 23 10:06:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B77C0180675 for ; Tue, 23 Oct 2018 10:06:03 +0200 (CEST) Received: (qmail 30598 invoked by uid 500); 23 Oct 2018 08:06:02 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 30555 invoked by uid 99); 23 Oct 2018 08:06:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2018 08:06:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3AFFDCF567 for ; Tue, 23 Oct 2018 08:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id vwK5mKVChcPY for ; Tue, 23 Oct 2018 08:06:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3F0675F42E for ; Tue, 23 Oct 2018 08:06:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 87AFDE0F4C for ; Tue, 23 Oct 2018 08:06:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3E5E1252B4 for ; Tue, 23 Oct 2018 08:06:00 +0000 (UTC) Date: Tue, 23 Oct 2018 08:06:00 +0000 (UTC) From: "DmitriyB. (JIRA)" To: dev@syncope.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (SYNCOPE-1386) Not committed managed objects can get into L2 cache. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SYNCOPE-1386?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] DmitriyB. updated SYNCOPE-1386: ------------------------------- Comment: was deleted (was: =C2=A0Do you have the property=C2=A0like "l2CacheClearTimeOut" settin= g which is responsible for clearing the L2 cache if nothing is happening wi= th it?) > Not committed managed objects can get into L2 cache. > ---------------------------------------------------- > > Key: SYNCOPE-1386 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1386 > Project: Syncope > Issue Type: Bug > Components: core > Affects Versions: 2.0.8 > Reporter: DmitriyB. > Priority: Major > Attachments: confirm_pwd_reset_action.sh > > > =C2=A0 > Hi guys. I noticed the issue that leads to inconsistent data that comes i= n response.=C2=A0 > =C2=A0 > Here is the use-case how to reproduce the problem:=C2=A0 > =C2=A0 > 1. Create user in Syncope=C2=A0 > 2. Do a request password reset action and make sure that token that is us= ed for pwd reset action is generated and stored into database.=C2=A0 > 3. Restart your application to be sure that L2 cache is empty.=C2=A0 > 4. Confirm password reset action for this user and make sure that request= ed password doesn't apply the password rules. In my case password is too sh= ort. The exception like "InvalidUser:InvalidPassword: Password too short" s= hould be thrown.=C2=A0 > 5. Request the user by username. The user that comes in HTTP Response doe= sn't have "token" and "tokenExpireTime" attributes. But you may find "token= " and "tokenExpireTime" value in SyncopeUser table for this user.=C2=A0 > =C2=A0 > I also noticed that ~ after 5 minutes left the L2 cache is gone. > You can find an example in confirm_pwd_reset_action.sh script. Run this c= ommand to execute the script:=C2=A0 > "./confirm_pwd_reset_action.sh | tee temp.log"=C2=A0 > Here I'm trying to do confirm-password-reset action after 5 minutes of wa= iting with the password that doesn't match the rules. And then I'm requesti= ng user by username. In response it comes without "token" and "tokenExpireT= ime". > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)