tachyonicproject / infinitystone Goto Github PK

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

This is with running sqlite

To reproduce:

$ token=`curl -H "Content-Type:application/json; charset=utf-8" -d '{"username": "root","password": "password"}' http://localhost/api/v1/token | grep token | awk -F \" '{print $4}'`
$ tenant_id=`curl -H "Content-Type:application/json; charset=utf-8" -H "X-Auth-Token:$token" -d '{"name": "test"}' http://localhost/api/v1/tenant | grep id | awk -F \" '{print$4}'`
$ curl -H "Content-Type:application/json; charset=utf-8" -H "X-Auth-Token:$token" -X "POST" http://localhost/api/v1/rbac/user/00000000-0000-0000-0000-000000000000/b5222990-2578-49ad-81e4-02d1082c9ad5/none/$tenant_id

Then:

curl -H "Content-Type:application/json; charset=utf-8" -H "X-Auth-Token:$token" -X "POST" http://localhost/api/v1/rbac/user/00000000-0000-0000-0000-000000000000/b5222990-2578-49ad-81e4-02d1082c9ad5/default/$tenant_id

results in:

{
    "error": {
        "title": "500 Internal Server Error",
        "description": "UNIQUE constraint failed: luxon_user_role.role_id, luxon_user_role.tenant_id, luxon_user_role.user_id"
    }
}

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

The Tenant selection view should only list Tenants for which the current logged in user has AT LEAST ONE role.

Credentials for Management.

For elements that already have interfaces configured with metadata, special care must be taken when the "encrypt_metadata" option is toggled. As it is at the moment, either All element interface metadata must be encrypted, or clear text. (can't have a mix). Or perhaps update so that this can be chosen on a per-interface basis

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

When user logs into region and switches region to another identity service the following is needed:

user_id and username is to be in the token, so user can be identified as new user and created within region if not existing. This is needed to be able to assign roles in the roaming region.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.

Complete Blueprint / Flow Design / Implementation Doc Updates / Unit Testing.