-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
Testable
-
-
https://pagure.io/fedora-infrastructure/issue/12075
- What is the application main URL? https://console-openshift-console.apps.kfluxfedorap01.toli.p1.openshiftapps.com
- Who will be the main contact for the application, or will this be core infrastructure? – Gal Ben Haim, Konflunx Infra (konflux-infra@redhat.com)
- What privacy policy will be applicable to the application, or will this be – Not Sure
the standard Fedora privacy policy?
Some more OIDC specific information then: - Which redirect URI(s) will the application use?
- flask-oidc defaults to: ``<APPLICATION_URL>/oidc_callback``
but it's configurable (so double-check) - Does the application need the user names, or will an application-specific
pseudonym suffice? - ie: using flask-oidc, do you ever rely on ``OIDC.user_getfield('sub')`` to
get the user's username. If not, this question likely does not matter for
your application - Which authorization flow does the application use?
- flask-oidc: authorization_code
- Which token authentication method does the application use?
- flask-oidc: client_secret_post
- Which response type does the application rely on?
- flask-oidc: Code