Diff for "Teams/Ams-Hackers"

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2017-01-20 12:27:07 →
Size: 1387
Editor: lukewm
Comment: Adding what I have so far regarding the implementations.
← Revision 7 as of 2017-02-21 12:23:58 → ⇥
Size: 1501
Editor: lukewm
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
## Keep the sections that seem useful for your team, add what you need, remove the rest... ##
Line 17: 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 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.
Line 21: Line 20:
== Collaboration Pad ==

Note. This pad will be deleted if 30 days of inactivity occur. If anything is useful there, please transfer it.

https://pad.riseup.net/p/ams-hackers

== Architecture Graphs ==

http://lukewm.gitlab.io/graphs/
Line 32: Line 21:

Please find the provider implementation here: https://gitlab.com/lukewm/oidcp/

Please refer to the ``README.md`` for building and finding the documentation		 https://gitlab.com/lukewm/oidcp/
Line 38: Line 24:
=== UX Design ===
Line 41: Line 27:
=== 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 [[https://gitlab.com/lukewm/oidcp/blob/master/test/conftest.py|oidcp/test/conftest.py]].

 * Request End-user resources from the Back-end.
Line 42: Line 37:

On the way ...		 https://gitlab.com/lukewm/fsfe-cd/

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 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.

Hacking

OpenID Connect Provider Implementation

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

OpenID Connect RP (Front-end) Implementation

UX Design

On the way ...

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/.
  • Request End-user resources from the Back-end.

OpenID Connect Rp (Back-end) Implementation

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

Category/Teams