@@ -226,6 +226,39 @@ authorization request and accepted by the user.
226
226
227
227
resp = self.rph.get_user_info(state_key)
228
228
229
+ :py:meth: `oidcrp.RPHandler.has_active_authentication `
230
+ After a while when the user returns after having been away for a while
231
+ you may want to know if you should let her reauthenticate or not.
232
+ This method will tell you if the last done authentication is still
233
+ valid or of it has timed out.
234
+
235
+ Usage example::
236
+
237
+ resp = self.rph.has_active_authentication(state_key)
238
+
239
+ response will be True or False depending in the state of the authentication.
240
+
241
+ :py:meth: `oidcrp.RPHandler.get_valid_access_token `
242
+ When you are issued a access token they normally comes with a life time.
243
+ After that time you are expected to use the refresh token to get a new
244
+ access token. There are 2 ways of finding out if the access token you have
245
+ passed their life time. You can use this method or you can just try using
246
+ the access token and see what happens.
247
+
248
+ Now, if you use this method and it tells you you have an access token
249
+ that should still be usable. That is no guarantee that that is the case.
250
+ things may have happened on the OPs side that makes the access token
251
+ invalid. So if this method only returns a hint as to the usability of the
252
+ access token.
253
+
254
+ Usage example::
255
+
256
+ resp = self.rph.get_valid_access_token(state_key)
257
+
258
+ Response will be a tuple containing with the access token and the
259
+ expiration time (in epoch) if there is a valid access token otherwise an
260
+ exception will be raised.
261
+
229
262
----------------
230
263
RP configuration
231
264
----------------
@@ -263,6 +296,17 @@ redirect_uris
263
296
behavior
264
297
Information about how the RP should behave towards the OP/AS
265
298
299
+ keys
300
+ If the OP doesn't support dynamic provider discovery it may still want to
301
+ have a way of distributing keys that allows it to rotate them at anytime.
302
+ To accomplish this some providers have choosen to publish a URL to where
303
+ you can find their OPs key material in the form of a JWKS.
304
+
305
+ Usage example::
306
+
307
+ 'keys': {'url': {<issuer_id> : <jwks_url>}}
308
+
309
+
266
310
If the provider info discovery is done dynamically you need this
267
311
268
312
client_prefs
0 commit comments