From Fedora Project Wiki

< User:Laxathom

Revision as of 10:13, 26 August 2015 by Laxathom (talk | contribs) (What left to be done for a staging instace: Remove packages already in fedora)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Note.png
This is a draft
This is a draft of potential features for FAS v3.0. It is meant to spawn discussion and will most likely evolve in the future.


Mockups

  • FAS 2 as reference


Goals

  • Move web framwork from TurboGears 1 (no longer maintained upstream) to Pyramid.
  • Provide a real/dedicated endpoint API.
  • Provide a better group's membership management/workflows.
  • Improved database model/Provide different backend.
  • Make it Fedora agnostic.
  • Provide new features (see below).
  • Provide a better administration management.
  • Provide a dynamic configuration management.
  • Make it Social-network friendly.

Features

Groups and people visibility

No need to log in anymore to review groups and people's profile (only public info will be disapled).

RESTful API

Provide a dedicated ENDPOINT to retrive accounts' data.
Access to this API requires a generated token that people can get from their
profile's page.

Profile's status

We will introduce some new status for workflow we wanted to manage
  • on_vaction: allow contributors to set a better view of their current activity. Also usefull for Fedora-Hub
  • disable: allow contributors to disable their account which will lead a complete revokation of all access on fedora system.

Profile Avatar

People will be able to add an avatar to their profile (from a 3rd party service)
This avatar will be available to 3rd-party which can use it in their views or more.

Profile Bio

Allow people to write up a bio (view-able from their profile's page).

Group 3rd-party binding

As we (Fedora project) has a specific way of using group (i.e providing VCS access and the like)
group will provide a way to bind its ACLs to 3rd party in order to retrieve people or to give people
some rights to this 3rd party if its members exist from this 3rd party.
Current target for now is:
  • GitHub organization
Admin or group's admin could bind a group to a github organization's team.
Which, create github's team if not exist and add its members to it if its members exist on github.
If group is VCS related, create a github's repo if not exist already and give its members commit access.
  • Pagure
Same as github for the workflow.

Group ownership

Group's owner has been renamed to "principal Administrator" as group's admin can now
pass along their group's ownership to another admin of the same group.
Account's administrator can do the same.

Group's status

Introducing group's status that admin can manage to better track activities.
  • active
  • inactive: no more sync in between services
  • archive: access revoked

Group Membership status

A new status on membership to better track activities.
  • inactive: no more sync in between services for this member
  • archived: revokes any access this group provides. Also provides a way to track former group members (from the web view).

Group Membership management

  • User will be able to join a group without being sponsored or approved by an admin if group hasn't any rules to join.
  • Group role: Admin will be able to choose what kind of role a group can provide from pre-defined one.
Fact: Most of our current groups provide a "sponsor" role, which actually make no sense as this role has no effect where this group is being used.
Group's Admin can choose which role he/her want to upgrade a member to. No need to go through each role every time.
Pre-defined roles we are think about:
  • user
  • editor
  • sponsor
  • moderator
  • administrator
  • Membership requirement: user will have to proceed through different step (if need to be) in order to get approved based on group requirement such as:
    • ssh key: if group requires it. Members will receive an email/UI notification to update their profile for this group.
    • license agreement: same as above.
    • 2x factor auth: same as above.
    • Client certificate: group's admin will be able to attach a CA to a group and only members of this group will be able to get a client certificate to access target resources.

Settings panel

Account's admin will have a dashboard where they could manage account related elements
An overview with number of registerged people, groups, license, etc.

Also, they will be able to:

  • people management
    • Remove an account
    • Block, disable or archive account
  • groups management
    • Add, edit and remove groups
    • Block or archive groups
  • groups' types management
  • license agreement management
    • Add, edit and remove Licenses
    • Enable license at sign-up which flag the license signing as mandatory
  • private API access management
    • Generate private token for trusted applications

Account activities

A new page where people can review their account's activities with datetime, events and locations.
This feature will basically log every action a contributor made to its account as in it will be able to review the last time he/her logged in and from where.

Connected applications

  • Github
Allow people to connect their github account and share their public infos with Fedora services.
  • Twitter
Allow people to connect their twitter account and share their public infos with Fedora service. Enabling twitting fedora info on request.

2 factors authentication

This 2 factors auth will be required from every login request (web app including) which mean, if user active it, and want to log in to mediawiki, they will have to enter both login+password then 2nd factor.

Request from Patrick: Add an option which allow trusted apps to request login without 2xfactor auth.

Note.png
Note
A group can requires that a 2 factor auth has to be enabled for its members, which mean user won't be approved until they enable this feature. For approved members, they will received an email ask them to enable it. A time period could be necessary otherwise member will be set as inactive.
  • Gauth token or FreeOTP?
Optional 2nd auth wihch once activated.
  • Yubikey
This one will not be added as a combo with the login and password (i.e login+password+otp)
(as discussed last flock-2014).
  • Fido U2F (TBD)
Requires a FIDO key and a chrome browser.
a plugins for firefox should come out soon though.

LDAP backend

Add another users & groups dict by Changing SQL backend to LDAP's for groups and people management.

Ideas

Status

  • Demo instance:
URL: http://fas3-dev.fedorainfracloud.org (poke me on IRC #fedora-apps if page is blanc)
login: jbezorg
pass: jbezorg
  • Pyramid move Green check.png

Release 3.0

Features (being updating)

REST API
  • Public (user with token)
People infos Green check.png
Groups infos Green check.png
  • Private (trusted 3rd party with token and secret)
Login request Green check.png
Account permission request that user grant. Green check.png
Registration
  • registration by step Green check.png
  • License agreement at registration Green check.png
  • Send an email with a generated token to validation email/registration Green check.png
Search
  • Groups Green check.png
  • People Green check.png
Group Management [demo video]
  • group hierarchy Green check.png
  • Membership request (with visual feedback on status) Green check.png
  • Pending requests (also from user's drop-down menu) Green check.png
  • List members view with action per members Green check.png
  • Group's owner edit-able Green check.png
  • Join group when there's no requirements Green check.png
  • Github sync/binding Green check.png
People profile's page
  • Avatar Green check.png
  • Status update Green check.png
  • Bio Green check.png
  • Password update Green check.png
  • Access token Green check.png
  • Account activities Green check.png
  • Membership listing with contextual action from a drop-down menu Green check.png
Login failure
  • Lock account on pre-configured x login failure Green check.png
  • Lock account for a pre-configured time Green check.png
  • Reset password Green check.png
Admin dashboard
  • Create/edit/delete groups Green check.png
  • Create/edit/delete group type Green check.png
  • Create/edit/delete license agreement Green check.png
  • Create/edit/delete Certificate Green check.png
  • Edit/delete account Green check.png
Notification
  • Email
Group membership (request, removal, join, owner update, group update) Green check.png
People profile (update, password change, activities)
New license agreement
New group type
New group
New Certificate
  • Fedmsg Green check.png

What left to be done for a staging instace

  • Build the test suite.
  • Fas-client upgrade to new API Green check.png (Available here)
  • Ipsilon binding
  • python-fedora upgrade to new API Green check.png (Available here)
  • supybot-fedora upgrade to new API Green check.png (Available here)
  • Fedora staging services update (bodhi, tahir, pkgdb, etc)
  • Package 3rd party libs added to FAS3 (I will add them to copr at first place)
    • cryptacular
    • flufl.enum
    • fake-factory (optional but I want to add it)

Desktop rendering

  • v0.1
  • v0.5

Mobile rendering

  • v0.5

Release 3.1