Hi all, In an off-line discussion with Subash regarding the UI aspect of the password field, we decided to use above option #1. As "TextField" and "PasswordField" are peers in the UI context, and as "TextField" has several other attribute that are not required by "PasswordField", option #1 was selected.
1. Create a new "PasswordField" class similar to "TextField", in "org.wso2.carbon.governance.generic.ui.common.dataobjects" As per the secured store aspect of the "PasswordField" following challenges occur, *UI level challenges* When to encrypt the pass word fields content (should it be done in the UI side, or in the backend) and when to decrypt content (should the content be decrypted every time it is viewed in the UI, or should the viewer or operation using the encrypted content have the facility to decrypt as necessary). *API level challenges* In the API level there isn't a specific way to identify password (encrypted) fields. Therefore it is hard to determine when to encrypt and decrypt in this level. Thank you, SameeraK On Tue, Jul 29, 2014 at 1:35 AM, Sameera Kannangara <[email protected]> wrote: > Hi all, > > Currently RXTs do not support password fields and I'm working on > implementing this. > > This implementation has a UI aspect which masks the contents of password > fields when rendered in web browser, and secured store aspect where > contents of password field should be encrypted when storing, and should be > decrypted when retrieving. > > Considering the implementation of UI aspect of password field it can be > implemented in following ways, > > > 1. Create a new "PasswordField" class similar to "TextField", in > "org.wso2.carbon.governance.generic.ui.common.dataobjects" > 2. Add an attribute to "TextField" class, in > "org.wso2.carbon.governance.generic.ui.common.dataobjects" to determine > whether this text field should be viewed as a normal text field or as a > password field. > > > IMO as password field differ only by masking the content in the text > field, it is suitable to go with the 2nd solution. > > What other factors should be concerned when implementing the UI aspect of > password field for RXTs? > > Thank you, > SameeraK > > -- > Sameera Kannangara, > Software Engineer, > WSO2 Inc. > -- Sameera Kannangara, Software Engineer, WSO2 Inc.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
