Create User table and concept of admin users
Activity
Show:

Former user
made 2 changes21 March 2018 at 00:17
Status
Verified
Merged
Resolution
None
Ready for Release

Former user
updated the link20 March 2018 at 04:56None
This issue causes ZNTAMT-22

Former user
changed the status20 March 2018 at 03:41QA
Verified

Former user
made 2 changes2 February 2018 at 06:15
Status
Review
QA
Status
In Progress
Review

Former user
changed the assignee24 January 2018 at 04:43Unassigned

Former user

Former user
updated the description23 January 2018 at 05:16We might borrow the idea from Jenkins. If there is no user yet, display a hash in the console. User can authenticate using username admin and that hash.
This sub task should only focus on admin user creation (via REST endpoint for now) and database table creation. It should have role based ACL setup.
Implementation detail:
when MT starts, it will print an initial password to the log console and write to a file $HOME/initialPassword.
REST endpoint to create accounts
{code}
POST /api/account
// payload
{
"name": "John Smith",
"email": "jsmith@example.com",
"accountType": "Normal",
"roles": ["admin"],
"credentials": [{
"username": "devID",
"secret": ["d", "e", "v", "K", "E", "Y"]
}
]
}
{code}
Once an account is created, the initial password is no longer valid.
Another REST endpoint to query all accounts (admin only)
{code}
GET /api/account
{code}

Former user
updated the parent10 January 2018 at 01:30None
ZNTAMT-4

Former user
created the Issue10 January 2018 at 01:30Ready for Release
Details
Details
Assignee
Former user
Former user(Deactivated)Reporter
Former user
Former user(Deactivated)Sprint
None
Priority

Parent
More fields
Time tracking
More fields
Time trackingCreated 10 January 2018 at 01:30
Updated 21 March 2018 at 00:17
Resolved 21 March 2018 at 00:17
We might borrow the idea from Jenkins. If there is no user yet, display a hash in the console. User can authenticate using username admin and that hash.
This sub task should only focus on admin user creation (via REST endpoint for now) and database table creation. It should have role based ACL setup.
Implementation detail:
when MT starts, it will print an initial password to the log console and write to a file $HOME/initialPassword.
REST endpoint to create accounts
POST /api/account // payload { "name": "John Smith", "email": "jsmith@example.com", "accountType": "Normal", "roles": ["admin"], "credentials": [{ "username": "devID", "secret": ["d", "e", "v", "K", "E", "Y"] } ] }
Once an account is created, the initial password is no longer valid.
Another REST endpoint to query all accounts (admin only)
GET /api/account