login.prototype.getEnvDetail is missing the following in the error callback.

   $('body > div.mySpinner').hide();
   $('body > div.myHiddenDiv').show();

Like HomeApp, it would be nice to run the app within the cell to avoid security issues.

For usability improvement:

1. when running within the cell, Unit URL and cell name input fields can be removed.
2. should not open another tab

Currently 3 radio buttons are displayed.
Agreed to change to 3 checkboxes (only one can be selected at a time) so that when no checkmark means "RequireSchemaAuthz" is not set.

Need to fix the logic

Not only it is wrongly encoded, it is also wrong in logic.

Specification might be here.

When displaying other user's profile information, it is better to use jQuery's .text() method

Maybe we can put a logout button next to token (right hand side).

Cell Manager sends out wrongly escaped "__id" value.
Wrong: "https%253A%252F%252Fdemo.personium.io%252Fdixonsiu_en"
Expected: "https%3A%2F%2Fdemo.personium.io%2Fdixonsiu_en"

Issue

Sometimes the Cell and target external Role are not from the same Personium Unit.
For detail specifications, please refer to the API Reference.

REST API URL:

    "https://{UnitFQDN1}/{CellName1}/__ctl/ExtRole"

External Role URL:

    "ExtRole": "https://{UnitFQDN2}/{CellName2}/__role/__/{ExtRoleName}"

Solution

Should compare the UnitFQDN whether "personium-localunit" is applicable.

To Dos

Should convert same Unit FQDN to personium-localunit

1. External Role Registration
2. External Cell Registration
3. Display List

Current, the followings are missing.

1. Description
2. Uninstall button

Need to determine the specifications.

1. what files to modify when locale is assigned
2. should we support multilingual editing in one dialog

Use DataTables to render the following tables.

1. [Box] - [box名のアンカー] - [ACL edit icon]
2. [Info] - [Administration] - [ACL edit icon]

The following method will raise an exception when Description is not defined.

common.prototype.getProfileDescription = function(resJson) {
    var tempDescription = resJson.Description;
    if (sessionStorage.selectedLanguage === 'en' && tempDescription.en != undefined) {
        tempDescription = resJson.Description.en;
    }
    return tempDescription;
}

Sample profile.json in en folder.

{"CellType":"App","DisplayName":"Directory (Demonstration)"}

Currently a Box cannot be uninstalled. The following conditions must be met before the user manually delete a box.

1. Box must be empty
2. Role/Relation created during Box installation must be deleted manually
3. Box related messages (sent/received) must be deleted manually

Since the "X-Personium-Recursive" HTTP header is now available for Box resource. need to modify the delete operation when a Box is selected to support uninstallation.

Not only it is wrongly encoded, it is also wrong in logic.

Correct specification here

Mainly ACL table has UX issue.
[Info] - [Administration] - [ACL edit icon]
Search for this modal dialog id="editCellAclSettingModal"

The REST API from the Cell Manager.

https://pds-dev.areas-yui.com/u-naka11/__ctl/Rule(Name='logout',_Box.Name='null')

Expected REST API.

https://pds-dev.areas-yui.com/u-naka11/__ctl/Rule(Name='logout')

OR.

https://pds-dev.areas-yui.com/u-naka11/__ctl/Rule(Name='logout',_Box.Name=null)

Original developer kept mixing the method calls. It should be refactored.

Even though I entered the following URL, it stills display an error icon.

https://demo.personium.io/debug-profile-put02/__role/__/operator

Actually enabling the option only allow you to create a role with any permission. And no account is created.

Newer (3rd Generation) profiles that support multilingual display are not implemented in the Cell Creation routine. Folder structures must be considered when saving profiles to PDS.

According to the API Reference, the External Role Name (URL) is at most contains 6 slashes ("/").

    https://{UnitFQDN}/{CellName}/__role/__/{ExtRoleName}

Function externalRole.prototype.getExternalRoleInfo must be fixed.

Currently, only Unit administrator can use this app. It would be nice to allow app developer to check or manage his/her cell easily.

Cell Manager is definitely a killer app any app developer wants!!!

1. Suggestion 1

   1. Automatic: login parameter -> spinner -> login failed -> login form
   2. Manual: login form -> spinner -> login failed -> login form

2. Suggestion 2

   1. Automatic: login parameter -> spinner -> login failed -> login form
   2. Manual: login form -> login form + spinner on top -> login failed -> login form

1. Add Import/Export buttons to the Main panel.
   

2. Sample dialog.
   

Modify REST API calling method to support x-personium-recursive header (true/false) to delete resources with children.

Description

When image's src attribute is assigned with either one of the following values. The anonymous image is not displayed.

1. null
2. undefined
3. ""
   (Empty string)

Screen

Current ("image" is displayed instead of anonymous image)

Expected

Solution

Should not assign invalid value. The following methods basically has the same problem and should be refactored.

1. showCellProfileImage
2. showBoxProfileImage

Not only it is wrongly encoded, it is also wrong in logic.

Correct specification here

Currently it is assumed that it always return successfully. But sometimes, when it fails, the spinner does not stop.

Example for how to handle error.

    <script>
    $( "#success" ).load( "/not-here.php", function( response, status, xhr ) {
      if ( status == "error" ) {
        var msg = "Sorry but there was an error: ";
        $( "#error" ).html( msg + xhr.status + " " + xhr.statusText );
      }
    });
    </script>

Not only the validation are wrongly encoded, it is also wrong in logic.

1. uCollectionOdata.prototype.validateFolderName
2. uCollectionOdata.prototype.validateOdataName
3. uCollectionOdata.prototype.validateEngineServiceName

Specification might be here.

1. Use HomeApp's existing method (open another tab with URL parameters)
   1. Token
   2. Basic authentication
2. When rendering login.html, use the parameters to trigger a POST so that authentication information will not be displayed

The following option does not have any effect.