Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 20B54200D18 for ; Wed, 11 Oct 2017 16:23:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1F5351609E4; Wed, 11 Oct 2017 14:23:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6481E1609CA for ; Wed, 11 Oct 2017 16:23:03 +0200 (CEST) Received: (qmail 67455 invoked by uid 500); 11 Oct 2017 14:23:02 -0000 Mailing-List: contact issues-help@fineract.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.apache.org Delivered-To: mailing list issues@fineract.apache.org Received: (qmail 67445 invoked by uid 99); 11 Oct 2017 14:23:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2017 14:23:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E11D4196128 for ; Wed, 11 Oct 2017 14:23:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eqWEOGnJDbBT for ; Wed, 11 Oct 2017 14:23:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 032425FD01 for ; Wed, 11 Oct 2017 14:23: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 80A79E0E80 for ; Wed, 11 Oct 2017 14:23: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 3746125396 for ; Wed, 11 Oct 2017 14:23:00 +0000 (UTC) Date: Wed, 11 Oct 2017 14:23:00 +0000 (UTC) From: "thynn win (JIRA)" To: issues@fineract.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FINERACT-537) Audit log in and log out MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 11 Oct 2017 14:23:04 -0000 thynn win created FINERACT-537: ---------------------------------- Summary: Audit log in and log out Key: FINERACT-537 URL: https://issues.apache.org/jira/browse/FINERACT-537 Project: Apache Fineract Issue Type: Improvement Components: User Management Affects Versions: 1.0.0 Reporter: thynn win Assignee: Markus Geiss Currently there is an audit table and code base for logging other activities but sign in and sign out. We have had a couple of clients requesting audit for who is currently logged in or at least to be able to view who logged in and logged out when. Acceptance criteria: Whenever a user login or logout, an entry should be made to audit table with timestamp and username. It'd be great if you can record IP address also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)