Differences between revisions 8 and 9

Ams-Hackers

Information

Coordinator: Jonas Öberg (jonas)
Membership: Open
Principal mailing list: ams-hackers@q.fsfe.org
Description: A topical team to discuss and rewrite the FSFE's account management system (ams)

About us

What we do

We work to rewrite our account management system (AMS) in a modern way taking some inspiration from devops practices and ensuring we have an easily extendable and flexible solution which require minimal maintenance. We do this because our current AMS is not in the best state and very hard to work with. It can not be moved to another web server in its current state which is a blocker for migrating other services.

See our Teams/Ams-Hackers/Requirements specification for more details.

Hacking

OpenID Connect Provider Implementation

https://gitlab.com/lukewm/oidcp/

OpenID Connect RP (Front-end) Implementation

UX Design

Visit the UX-Design page.

Notes on Front-end implementation

The front-end should be responsible for two things:

Redirect the End-user to the provider, to authenticate.
- Send a request to /authorize/ with the correct parameters.
- Exchange the code received from the response for an identity token and access token via /token/.
  - For request example, check auth_params and token_params fixtures in oidcp/test/conftest.py.
Request End-user resources from the Back-end.

OpenID Connect Rp (Back-end) Implementation

https://gitlab.com/lukewm/fsfe-cd/

Category/Teams

-  ⇤ ← Revision 8 as of 2017-02-27 19:22:39 → 
  Size: 1519
  Editor: lusy
  Comment:
+   ← Revision 9 as of 2017-03-24 07:09:49 → ⇥
  Size: 1721
  Editor: jonas
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 17:
-We try to figure out WHAT we should do about our ams (which is not in the best state, and very hard to work with) and HOW it should look like. We also work on actually bringing the current system to the state of HOW. See our [[Teams/Ams-Hackers/Requirements]] specification for more details.
+We work to rewrite our account management system (AMS) in a modern way taking some inspiration from devops practices and ensuring we have an easily extendable and flexible solution which require minimal maintenance. We do this because our current AMS is not in the best state and very hard to work with. It can not be moved to another web server in its current state which is a blocker for migrating other services.

See our [[Teams/Ams-Hackers/Requirements]] specification for more details.

Diff for "Teams/Ams-Hackers"