Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-20 Thread Isura Karunaratne
On Mon, Mar 20, 2017 at 11:51 AM, Isura Karunaratne wrote: > Hi Omindu, > > > > On Mon, Mar 13, 2017 at 5:00 PM, Omindu Rathnaweera > wrote: > >> Hi, >> >> On Sun, Mar 12, 2017 at 7:59 AM, Ruwan Abeykoon wrote: >> >>> Hi All, >>> Can the hash

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-20 Thread Isura Karunaratne
Hi Omindu, On Mon, Mar 13, 2017 at 5:00 PM, Omindu Rathnaweera wrote: > Hi, > > On Sun, Mar 12, 2017 at 7:59 AM, Ruwan Abeykoon wrote: > >> Hi All, >> Can the hash algorithm change over the time? >> If so we need to record the hash algorithm used to do

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-19 Thread Sagara Gunathunga
On Sun, Mar 19, 2017 at 11:28 AM, Gayan Gunawardana wrote: > > > On Thu, Mar 16, 2017 at 8:44 PM, Sagara Gunathunga > wrote: > >> >> >> On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana >> wrote: >> >>> Hi All, >>> >>> We are in the process of

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-18 Thread Gayan Gunawardana
On Thu, Mar 16, 2017 at 8:44 PM, Sagara Gunathunga wrote: > > > On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > >> Hi All, >> >> We are in the process of implementing password history validation feature >> for IS 6.0.0. Architecture of this feature

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-16 Thread Sagara Gunathunga
On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > Hi All, > > We are in the process of implementing password history validation feature > for IS 6.0.0. Architecture of this feature was previously discussed in [1] > by Isura for IS 5.3.0. We plan to follow same

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-16 Thread Imesh Gunaratne
On Thu, Mar 16, 2017 at 9:39 AM, Gayan Gunawardana wrote: > > On Wed, Mar 15, 2017 at 10:19 AM, Imesh Gunaratne wrote: >> >> >> ​Would you mind explaining the purpose of the field SALT_VALUE? >> > > In order to compare user given password with stored password

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-15 Thread Gayan Gunawardana
Hi Imesh, On Wed, Mar 15, 2017 at 10:19 AM, Imesh Gunaratne wrote: > On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > >> >> CREATE TABLE IF NOT EXISTS IDN_PASSWORD_HISTORY_DATA ( >> ID INTEGER NOT NULL AUTO_INCREMENT, >> USER_UNIQUE_ID

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-15 Thread Dilan Udara Ariyaratne
On Mon, Mar 13, 2017 at 5:00 PM, Omindu Rathnaweera wrote: > Hi, > > On Sun, Mar 12, 2017 at 7:59 AM, Ruwan Abeykoon wrote: > >> Hi All, >> Can the hash algorithm change over the time? >> If so we need to record the hash algorithm used to do hashing along with

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-14 Thread Imesh Gunaratne
On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > > CREATE TABLE IF NOT EXISTS IDN_PASSWORD_HISTORY_DATA ( > ID INTEGER NOT NULL AUTO_INCREMENT, > USER_UNIQUE_ID VARCHAR(255) NOT NULL, > SALT_VALUE VARCHAR(255), > HASHVARCHAR(255) NOT NULL, >

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-13 Thread Omindu Rathnaweera
Hi, On Sun, Mar 12, 2017 at 7:59 AM, Ruwan Abeykoon wrote: > Hi All, > Can the hash algorithm change over the time? > If so we need to record the hash algorithm used to do hashing along with > the particular password history record. We need to use the particular > algorithm to

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-12 Thread Isura Karunaratne
Hi Joahnn, On Mon, Mar 13, 2017 at 9:14 AM, Johann Nallathamby wrote: > > > On Mon, Mar 13, 2017 at 9:03 AM, Isura Karunaratne wrote: > >> Hi Gayan, >> >> >> On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana >> wrote: >> >>> Hi All, >>> >>>

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-12 Thread Gayan Gunawardana
On Mon, Mar 13, 2017 at 9:03 AM, Isura Karunaratne wrote: > Hi Gayan, > > > On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > >> Hi All, >> >> We are in the process of implementing password history validation feature >> for IS 6.0.0. Architecture of

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-12 Thread Johann Nallathamby
On Mon, Mar 13, 2017 at 9:03 AM, Isura Karunaratne wrote: > Hi Gayan, > > > On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > >> Hi All, >> >> We are in the process of implementing password history validation feature >> for IS 6.0.0. Architecture of

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-12 Thread Isura Karunaratne
Hi Gayan, On Sun, Mar 12, 2017 at 7:44 AM, Gayan Gunawardana wrote: > Hi All, > > We are in the process of implementing password history validation feature > for IS 6.0.0. Architecture of this feature was previously discussed in [1] > by Isura for IS 5.3.0. We plan to follow

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-11 Thread Gayan Gunawardana
On Sun, Mar 12, 2017 at 7:59 AM, Ruwan Abeykoon wrote: > Hi All, > Can the hash algorithm change over the time? > In general practice this will be a one time configuration. > If so we need to record the hash algorithm used to do hashing along with > the particular password

Re: [Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-11 Thread Ruwan Abeykoon
Hi All, Can the hash algorithm change over the time? If so we need to record the hash algorithm used to do hashing along with the particular password history record. We need to use the particular algorithm to do the comparison, not the system configured one. Cheers, Ruwan On Sun, Mar 12, 2017

[Architecture] [C5][IS 6.0.0] Password History Validation

2017-03-11 Thread Gayan Gunawardana
Hi All, We are in the process of implementing password history validation feature for IS 6.0.0. Architecture of this feature was previously discussed in [1] by Isura for IS 5.3.0. We plan to follow same architecture with minor changes. Previously history validation has been done by checking only