-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #63 from IdentityPython/develop
Version 2.0
- Loading branch information
Showing
229 changed files
with
12,425 additions
and
6,920 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
# The IdpyOIDC client | ||
|
||
A client can send requests to an endpoint and deal with the response. | ||
|
||
IdpyOIDC assumes that there is one Relying Party(RP)/Client instance per | ||
OpenID Connect Provider(OP)/Authorization Server (AS). | ||
|
||
If you have a service that expects to talk to several OPs/ASs | ||
then you must use **idpyoidc.client.rp_handler.RPHandler** to manage the RPs. | ||
|
||
RPHandler has methods like: | ||
- begin() | ||
- finalize() | ||
- refresh_access_token() | ||
- logout() | ||
|
||
More about RPHandler at the end of this section. | ||
|
||
## Client | ||
|
||
A client is configured to talk to a set of services each of them represented by | ||
a Service Instance. | ||
|
||
# Context | ||
|
||
# Service | ||
|
||
A Service instance is expected to be able to: | ||
|
||
1. Collect all the request arguments | ||
2. If necessary collect and add authentication information to the request attributes or HTTP header | ||
3. Formats the message | ||
4. chooses HTTP method | ||
5. Add HTTP headers | ||
|
||
and then after having received the response: | ||
|
||
1. Parses the response | ||
2. Gather verification information and verify the response | ||
3. Do any special post-processing. | ||
3. Store information from the response | ||
|
||
Doesn't matter which service is considered they all have to be able to do this. | ||
|
||
## Request | ||
|
||
## Response | ||
|
||
# AddOn | ||
|
||
# Endpoints | ||
|
||
## OAuth2 | ||
|
||
- Access Token | ||
- Authorization | ||
- Refresh Access Token | ||
- Server Metadata | ||
- Token Exchange |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
# An entity that can act both as a server and a client |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
|
||
# Service | ||
|
||
## Request | ||
|
||
## Response | ||
|
||
# Context | ||
|
||
# AddOn |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.