fix rst warnings
Fixes a bunch of warnings -- mostly title underscores not matching the titles Signed-off-by: Ryan Lerch <rlerch@redhat.com>
This commit is contained in:
parent
86b8a42a67
commit
89e13e4513
4 changed files with 10 additions and 10 deletions
|
@ -10,7 +10,7 @@ to create an ouath2 webserver flow which validates based on oidc tokens.
|
|||
This needs to be replaced using a new library.
|
||||
|
||||
Authlib
|
||||
------
|
||||
-------
|
||||
Authlib has the functionality to follow this flow and use oidc on top of oauth2
|
||||
functionality https://docs.authlib.org/en/latest/client/oauth2.html#oauth-2-openid-connect
|
||||
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
Flask-oidc
|
||||
========
|
||||
==========
|
||||
|
||||
Purpose
|
||||
-------
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
Oauthlib vs Authlib
|
||||
=====================
|
||||
===================
|
||||
|
||||
Resources
|
||||
---------
|
||||
|
@ -9,7 +9,7 @@ Resources
|
|||
|
||||
|
||||
Discussion
|
||||
---------
|
||||
----------
|
||||
Which library should be used to replace the currently used and deprecated
|
||||
oauth2client. The two main contenders are Oauthlib and Authlib.
|
||||
|
||||
|
@ -19,7 +19,7 @@ https://github.com/lepture/flask-oauthlib#readme
|
|||
|
||||
|
||||
Conclusion
|
||||
---------
|
||||
----------
|
||||
Authlib seems to be the best candidate for this initiative. There is knowledge
|
||||
in the team of the library as it was used in bodhi. It also appears to have an
|
||||
easier to implement and has a flask integration and is recommended for use by
|
||||
|
|
|
@ -34,8 +34,8 @@ We have three options:
|
|||
|
||||
Currently we are proposing primarily the first option.
|
||||
|
||||
Preliminary notes on maintianing current FMN
|
||||
--------------------------------
|
||||
Preliminary notes on maintaining current FMN
|
||||
--------------------------------------------
|
||||
|
||||
Based on Pierre's POC, FMN is upgrade-able to recent versions
|
||||
of python and its libraries.
|
||||
|
@ -53,7 +53,7 @@ Outstanding issues to be tackled by the initiative:
|
|||
|
||||
|
||||
Preliminary notes on using other off-the-shelf applications
|
||||
-------------------------------------
|
||||
-----------------------------------------------------------
|
||||
|
||||
As we want people to be able to get notified on messages on the bus,
|
||||
we'd need to integrate with our fedora-messaging infrastructure and our
|
||||
|
@ -62,9 +62,9 @@ fullfil all of the needs FMN currently serves
|
|||
|
||||
|
||||
Create a new bespoke application that better suits our needs
|
||||
----------------------------------------------------
|
||||
------------------------------------------------------------
|
||||
|
||||
This is an option we'd take if and only if the path of maintaining the original application
|
||||
was not feasible, or there was some way to greatly simplify the new implementation.
|
||||
|
||||
With FMN neither is the case.
|
||||
With FMN neither is the case.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue