Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Date: Mon, 21 Feb 2011 10:06:38 +0000 (UTC)
From: =?utf-8?Q?Reto_Bachmann-Gm=C3=BCr_=28JIRA=29?= <jira@apache.org>
To: clerezza-dev@incubator.apache.org
Message-ID: 
 <697138831.5489.1298282798553.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1272534912.14877.1297695537570.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Closed: (CLEREZZA-421) Support for multiple user password
 encryptions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLEREZZA-421?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reto Bachmann-Gm=C3=BCr closed CLEREZZA-421.
---------------------------------------

    Resolution: Fixed

Thanks Daniel for the very good patch

> Support for multiple user password encryptions
> ----------------------------------------------
>
>                 Key: CLEREZZA-421
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-421
>             Project: Clerezza
>          Issue Type: New Feature
>            Reporter: Daniel Spicar
>            Assignee: Reto Bachmann-Gm=C3=BCr
>         Attachments: patch-CLEREZZA-421.diff
>
>
> We have an issue when we import users from a different system to clerezza=
. The users have passwords encrypted in SSHA (not SHA-1 as clerezza uses). =
We do not have their clear-text passwords.
> Now I wonder how would you best enable clerezza to support logins with di=
fferent password encoding methods. Most likely a single user will only use =
one encoding but different users can have different encodings.=20
> I have seen you have WeightedAutenicationMethod services. But if I interp=
ret this correctly it won't solve my issue. I assume I am looking for a way=
 to register multiple AutenticationChecker services such that passwords can=
 be checked against more than one of them. I don't see this implemented so =
far.
> Some questions with this would be:
> - do we simply add new properties for differently encoded passwords (pass=
wordSsha, passwordSha1, ...) or do we change the ontology so a password res=
ource contains both, the encrypted string as a literal and a uri designatin=
g the password encoding method?
> - can the user have more than one such password resources (the password e=
ncoded in multiple encryption methods)?
> - how to update user passwords? (e.g. delete all passwords and add a new =
one in the default encoding of the platform)=20
> I could provide a patch for this issue but we should define how we want t=
o resolve it first.

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira