A more generic Password class

7 views
Skip to first unread message

Iren Tuna

unread,
Sep 7, 2014, 6:26:29 PM9/7/14
to openen...@googlegroups.com
Hi,

It should be possible to authenticate a user by a certain connector, and another one by another connector. For example: user1 by usernamepasword, and user2 by the other connector. It is not known beforehand which user by which connector.

Currently, the usernamepassword connector has its own "Password" class. In OpenEngSBWebSession this class is used for login. In order that another authentication connector could try to authenticate the user as well,
* either a dependency is required from the new connector to the usernamepassword connector for the Password class,
* or a more generic Password class should be introduced that would be common to and supported by both of these connectors and used by the OpenEngSBWebSession.

The second alternative seems to be the better one from the point of good design. Then the question would be where to put this common Password class. Possible options at first sight:
* org.openengsb.core.api.security.model
* org.openengsb.domain.authentication

I would like to read the opinions for the most reasonable place to put the Password class.

Regards,
iren

Reply all
Reply to author
Forward
0 new messages