Should allow this:

/api/user?limit=10&skip=20&q=.... ?

Currently prompts the user if they're missing an @ but not a .

Hey @mirceaalexandru from our conversation.

Every client route has to pass this check otherwise it gets sent back to the root to login:

https://github.com/nearform/concorda/blob/master/client/bootstrap/createRootComponent.js#L20

Because we no longer have a token this fails. We need to change this so it hits the server and validates the current cookie. If this fails we should redirect otherwise. We can drop the token for good then.

The current build of Concorda is kicking you when you're logged in and delete the user you're currently logged in as, but only when you navigate to Overview, and then back to Users.
The user should be kicked once the delete themselves, to prevent them from deleting other users afterwards.

Should work the same as Vidi. These should map directly to seneca calls. You'll need these to power the ui.

@ckiss @mirceaalexandru both assigned.

@mirceaalexandru I'll assign yourself to this next week. You will be the lead maintainer for both the plugin and the dashboard yay! :D

We should probably have this in it's own toolbox above the list.

The feedback was once the list grew too long the button would be at the bottom.

The bug icon contains a link to the vidi-dashboard github issues page instead of the concorda issues page.

Related with senecajs/seneca-web#42

We need a ui component that handles editing a 'user'

we can do it like this:

1. add permissions to each user from a set of defined permission types.
2. create groups with set of permissions and then assign users to groups.
3. mix of the above, so you can assign an user to a group and then override a certain permission specially for that user by direct assigning of that permission. This method offers a greater flexibility and also allows us to implement in two stages - first directly assign permission and in another iteration add group support.
4. Other approaches?

Let's move the vidi UI to concorda so we can worry about adding features.

You can remove the vidi specific backend stuff, keep the login. @ckiss has a good idea of vidi so can show you what needs to be moved.

Post demo we've had requests to make the UI around searching and dealing with the user more refined. We basically need,

• Search bar with, dropdown for target column, plus clear search
• Back / Next buttons
• Ascend / Descend buttons per column (not sure it will look on mobile)
• xxx of yyy label for current / total row counts (pagination)
• Plus current bits on screen

@thefoxis I'm keen to see how this will fit on mobile. Ultimately it's just a searchable list of users. If the table format is too restrictive I'm happy for you to comment it out and add in a hardcoded list that better suits our need, we can very quickly break down into components to make it work as needed. We are talking about the possibility of 10,000 users; I'm keen ensure the user experience is not impacted by this scale, even on mobile, so I'd rather you had no restriction to tables on this.

We may have a view more fields to come yet so I would probably edge more towards a searchable 'card' view but we need to have as many rows on screen as possible too.

Note for me once @thefoxis has a stable point for me to move from. Related to vidi-insights/vidi-dashboard#53

With changes made to the sidebar to move it to the shell the login now renders in the same area as pages. This means we have a little space to the left of the login box where the sidebar usually sits. In the case of login and some other screens down the line can we get a full page class to style this away?

I would be applying it here: https://github.com/nearform/concorda/blob/master/client/containers/shell.js#L23

I think something like page-wrapper-full would do perfect.

When the size of the page is greater than the viewport the header and sidebar scroll away. Can we make it so only the inner portion or 'page' scrolls when taller than the viewport?

1. Auth token should not be preserved in the store.
2. On each action, the /auth/user should be requested to make sure the user is still loggedIn.

These changes should be applied also for Vidi.

Same as vidi-insights/vidi-dashboard#54

If you edited User1's email to be the same as User2's it allows it.
Also, it doesn't change the email of User1, but changes the name of User2 to match User1.
You then have 2 User1 with 2 different email address.

You should have two pages, one for listing all users, another for editing a single user. We need enough redux functionality to:

• add user
• edit user
• list users
• delete user

Use basic markup, we will get both pages styled properly after it's functional.

@ckiss @mirceaalexandru Assigned to both.

When the user selects to edit an account, only the name and email can be changed and not the password.

All fields have no limit for char . And if you adding long names its spoiling view of table.
Password has no any requirements .
How to recover password if forgotten?
Email don't need to be real.
Any protection from Cross-site scripting?

I believe there's no class added to login form h2 when the innerText is changed to an error message. I need that to be able to turn it into an alert.

This will form the basis of our first demo.

• Do a full copy of seneca-mvp
• Remove any non 'user management' specific stuff
• Add a transport pin to listen for 'role:user,cmd:*' to manage external messages.

We don't yet have a logo for Concorda. It is a user management system so I am thinking some sort of simple user Icon for now would be great. You are totally free to design the actual icon with all the glory that goes with it but for now a temporary user head will do perfect.

Could you recommend complementary colors for Concorda, it is the same UI as vidi. We just want to shift the palette to green. I just need the hex codes and variable names, I can add them to the code once I move over some changes.

@thefoxis I'll push this out until Monday as the default styles you have included make it look semi styled already. In this instance all of the content and data is hooked up. You are free to modify the markup as needed. I'll chat to you Monday about any additional state you need to drive the UI.

The routes are,

• /user
• /user/add/
• /user/edit

Add and edit are the exact same, just different context. Both have a simple editor form. The main route has a list of users with some buttons to add / edit / delete each one.

Flow:

• login in one app
• when start another app from same browser/IP then we should try to login automatically - This is not implemented as a feature but I can add it.
  Anyway we need a way to identify the user based on something.(edited)

Question: Is that OK it will have the same login identifier (auth token set as cookie value) for both sessions or a new login will be created?
My answer: a new login will be created based on the existing one.

Question: What will be the discriminator for user in shared login feature? Remote client IP? Other?

Question UI: For shared login it will require a change in UI. When go to login page verify if already logged in in another apps and then:

• automatically login - then it will not be possible for a user to login using different credentials as login page will never be accessible.
• or display a button for automatically login

Tasks for this iteration:

• #5 - Add login
• #6 - Integrate Vidi login
• #7 - Add register/update user

I've added a favicon here but unsure about the asset pipeline. The path to image is assets/img/favicon.png, no errors are thrown but just want an additional pair of 👀 to make sure this is correct to be serving this asset. Right now Chrome thinks it's text/html, not an image.

We will need support for:

• limit - to limit number of items returned
• skip - to skip a number of items
• order - control order of users.

This is required as we will need pagination for user list.

For Friday

We need the templates before we can make the editor and list pretty.

@ckiss @mirceaalexandru both assigned.

When you log in and fail the username and password stay in the box, this should not happen, instead when a login error is detected the values should be cleared.

Adding a user does not add to the list of users

We need to be able to list all users in concorda. We'll use #10 to edit them.

This feature will force user on remote app to be redirected to login page automatically.

• New component
• Should have clear button
• Dropdown to select column to search
• Columns provided via props
• Emits onSearch(term, target)