[jira] [Commented] (DIRSTUDIO-1115) Value editor settings are not used and the menu displays wrong entries

[Stefan Seelmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15501516#comment-15501516
 ] 

Stefan Seelmann commented on DIRSTUDIO-1115:


The text editor is only meant for string attributes (e.g. Directory String 
attributes), but also works for binary attributes if it can be UTF-8 decoded to 
a string. (There is some inconsistency in handling binary values that I'll fix.)

But in your case, if the encoding is unknown, we would need a more enhanced 
editor where you can choose the encoding in the editor windows and then the 
editor tries to decode the value and let you edit it.


> Value editor settings are not used and the menu displays wrong entries
> --
>
> Key: DIRSTUDIO-1115
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1115
> Project: Directory Studio
>  Issue Type: Bug
>  Components: studio-ldapbrowser
>Affects Versions: 2.0.0-M10 (2.0.0.v20151221-M10)
> Environment: Windows 7 x64
> Linux Debian 8.5 x64
>Reporter: Nagy Attila
>Priority: Minor
>
> The following two issues are really close related to each other, so I'm 
> reporting them here together. If they should be reported separately, then 
> please indicate so, and I'll separate them.
> I was trying to set custom value editor for some attributes (vacationInfo 
> octet stream) when I discovered that the settings are ignored. I added a new 
> entry into Value Editors (Eclipse Preferences -> LDAP Browser -> Value 
> Editors):
> attribute: vacationInfo
> value editor: "Text Editor"
> Applied the settings (even restarted Eclipse) but on double clicking a 
> vacationInfo attribute nothing happens, not even if I right click and select 
> "Edit Value". The only way to edit the attribute value is to right click the 
> attribute, select "Edit Value With" and there selecting "Hex Editor".
> While I was messing with these settings I noticed that the "Edit Value With" 
> submenu contains a changing entry (top one, besides the alternative editors 
> and the "Preferences..." one) which as I found out is the entry corresponding 
> to the previously selected attribute. So if selecting a password, afterwards 
> selecting a string attribute  and then looking into the "Edit Value With" 
> submenu, it will contain a "Password Editor" entry which will do nothing. And 
> sometimes it does really weird things.
> Eg:
> Selecting a Boolean and afterwards a Password: the "Boolean Editor" entry is 
> displayed but it opens the "Password Editor".
> Selecting a Password and afterwards a Boolean: the "Password Editor" entry is 
> displayed but it opens the "In-Place text Editor".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FC-144) Ability to assign groups to roles

[Shawn McKinney (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FC-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn McKinney updated FC-144:
--
Affects Version/s: (was: 1.0.0-RC40)
   1.0.1
Fix Version/s: 1.0.2

> Ability to assign groups to roles
> -
>
> Key: FC-144
> URL: https://issues.apache.org/jira/browse/FC-144
> Project: FORTRESS
>  Issue Type: Improvement
>Affects Versions: 1.0.1
>Reporter: Florin Stingaciu
>Assignee: Vyacheslav Vakhlyuev
> Fix For: 1.0.2
>
>
> We are currently working on performing an integration between Openstack 
> Keystone and Fortress Core. We will use Fortress as the authorization backend 
> for the rest of Openstack. We have managed to map most of the current 
> functionality in Openstack within the Fortress schema except for the ability 
> to assign roles to a group. 
> I've spoken with [~smckinney], and he determined this improvement is a 
> feasible addition to Fortress's feature set. After a number of back and 
> forths, we have come up with the following requirements as API additions:
> * Session createSession (Group group, boolean isTrusted);
> * void assignGroup ( Group group, Role role );
> * List roleGroups ( Role role );
> * List groupRoles ( Group group );
> * the ability to use the above session with checkAccess(Session session, 
> Permission perm)
> We also discussed temporal constrains for group to role assignment. Temporal 
> constrains will not be utilized as this functionality has not been defined in 
> Openstack.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FC-179) [ fortress-web ] Firefox 48 broke Selenium tests

[Shawn McKinney (JIRA)]

Shawn McKinney created FC-179:
-

 Summary: [ fortress-web ] Firefox 48 broke Selenium tests
 Key: FC-179
 URL: https://issues.apache.org/jira/browse/FC-179
 Project: FORTRESS
  Issue Type: Bug
Affects Versions: 1.0.1
Reporter: Shawn McKinney
Assignee: Shawn McKinney
 Fix For: 1.0.2


Upgrading to firefox v48 broke the selenium tests.  This requires upgrading to 
use selenum v3 along with using WebDriverManager to automatically download 
latest driver to machine.

  io.github.bonigarcia
  webdrivermanager
  1.4.9
  test


more info here:
https://github.com/bonigarcia/webdrivermanager



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)